Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da41dd891965280f607e5784fa807e52b2e2646bdcfca244a3e2c30134781b2

Tx prefix hash: c376689239a8c1c16ea1869eb10507a26f7e53b8422d20f4a2dd37527f23ff09
Tx public key: a54ad41c686d8075c32eac9e883d56c8dd9e2a6b6af9dd74d23050724a13e95d
Timestamp: 1706236624 Timestamp [UCT]: 2024-01-26 02:37:04 Age [y:d:h:m:s]: 01:117:03:31:36
Block: 943419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344857 RingCT/type: yes/0
Extra: 01a54ad41c686d8075c32eac9e883d56c8dd9e2a6b6af9dd74d23050724a13e95d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee783fb2ce3269eb9e1f30266aa05ad395e7e37db717ca73c730e79a0e8a1888 0.600000000000 1401625 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": 943429, "vin": [ { "gen": { "height": 943419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee783fb2ce3269eb9e1f30266aa05ad395e7e37db717ca73c730e79a0e8a1888" } } ], "extra": [ 1, 165, 74, 212, 28, 104, 109, 128, 117, 195, 46, 172, 158, 136, 61, 86, 200, 221, 158, 42, 107, 106, 249, 221, 116, 210, 48, 80, 114, 74, 19, 233, 93, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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