Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 45e129827c129ccc635a5b05bcfe28d314c235262731c8568bd96f30fe87623b

Tx prefix hash: 72556a4f9613cfd6edf2989264fc8dce07e5bf3d40a632c52b015eca4f2d76ab
Tx public key: b8c69a861810db123ca3422b04643db11f2d1a4baec523a193263b3e14df965c
Timestamp: 1734880747 Timestamp [UCT]: 2024-12-22 15:19:07 Age [y:d:h:m:s]: 00:099:03:18:06
Block: 1180829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70617 RingCT/type: yes/0
Extra: 01b8c69a861810db123ca3422b04643db11f2d1a4baec523a193263b3e14df965c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 405ea2b534671f8053f953653dc3cc42a1d7e9d4e09d1cd822397a44845f5ea9 0.600000000000 1667244 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1180839, "vin": [ { "gen": { "height": 1180829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "405ea2b534671f8053f953653dc3cc42a1d7e9d4e09d1cd822397a44845f5ea9" } } ], "extra": [ 1, 184, 198, 154, 134, 24, 16, 219, 18, 60, 163, 66, 43, 4, 100, 61, 177, 31, 45, 26, 75, 174, 197, 35, 161, 147, 38, 59, 62, 20, 223, 150, 92, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8