Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c814e0dad91170191daf6daef13f9ee0d72e36d62fc77fa0c226c283a1acf92

Tx prefix hash: 49b2e28f61f1ea4bd02d7184e4b9126f5086044de8ef2498c642aa84cb68bc6a
Tx public key: 51b70075a30e558f7cd3cfb98800b56f4d458592b0ab647738f5fc64bf7641e4
Timestamp: 1702403563 Timestamp [UCT]: 2023-12-12 17:52:43 Age [y:d:h:m:s]: 02:027:13:21:37
Block: 911696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539476 RingCT/type: yes/0
Extra: 0151b70075a30e558f7cd3cfb98800b56f4d458592b0ab647738f5fc64bf7641e4021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c149b7b5b42578f658cb2ea894af85ba458689d457a23e2bd8e1a18865cfb455 0.600000000000 1368912 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": 911706, "vin": [ { "gen": { "height": 911696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c149b7b5b42578f658cb2ea894af85ba458689d457a23e2bd8e1a18865cfb455" } } ], "extra": [ 1, 81, 183, 0, 117, 163, 14, 85, 143, 124, 211, 207, 185, 136, 0, 181, 111, 77, 69, 133, 146, 176, 171, 100, 119, 56, 245, 252, 100, 191, 118, 65, 228, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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