Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dd8997f8d251983db04cc72fa2fac126e9be2074f6ddbb384d36f470b694ecc

Tx prefix hash: d86b2820aee0645693b62a98616d406a455fcca23ca2b43b6d03660992a75139
Tx public key: 0e3aa88090677cf26dd4921853dbd370e0b5e2f6ad41aa1dc41f1ee2f7ad4909
Timestamp: 1699142262 Timestamp [UCT]: 2023-11-04 23:57:42 Age [y:d:h:m:s]: 01:085:23:46:54
Block: 884886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322375 RingCT/type: yes/0
Extra: 010e3aa88090677cf26dd4921853dbd370e0b5e2f6ad41aa1dc41f1ee2f7ad4909021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.717803140000 dcy

stealth address amount amount idx
00: ad7c437bf1d30ff00569951f292cb8a4e53640033685d987cdfc6cccb4fd784a 0.717803140000 1340635 of 0

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": 884896, "vin": [ { "gen": { "height": 884886 } } ], "vout": [ { "amount": 717803140, "target": { "key": "ad7c437bf1d30ff00569951f292cb8a4e53640033685d987cdfc6cccb4fd784a" } } ], "extra": [ 1, 14, 58, 168, 128, 144, 103, 124, 242, 109, 212, 146, 24, 83, 219, 211, 112, 224, 181, 226, 246, 173, 65, 170, 29, 196, 31, 30, 226, 247, 173, 73, 9, 2, 17, 0, 0, 0, 3, 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