Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e765da7f2706f4d670ec3b6d03f7b08a0a4b206110095ee63a51cb45c0ab77e3

Tx prefix hash: 0871b53e4ec3b732ca88b86f93159c9cf94de3530135861320a7f89d0380c1ab
Tx public key: 45b58eab6e293f5d8cc17b89f234ff71d425f2bf2940cd5c0174a6d2cfda486e
Timestamp: 1733587445 Timestamp [UCT]: 2024-12-07 16:04:05 Age [y:d:h:m:s]: 00:101:23:08:23
Block: 1170097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72684 RingCT/type: yes/0
Extra: 0145b58eab6e293f5d8cc17b89f234ff71d425f2bf2940cd5c0174a6d2cfda486e021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc33e8177d177d205ef9f4ac7a6829366352ec2d479da178b7108b90f63c2349 0.600000000000 1655826 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": 1170107, "vin": [ { "gen": { "height": 1170097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc33e8177d177d205ef9f4ac7a6829366352ec2d479da178b7108b90f63c2349" } } ], "extra": [ 1, 69, 181, 142, 171, 110, 41, 63, 93, 140, 193, 123, 137, 242, 52, 255, 113, 212, 37, 242, 191, 41, 64, 205, 92, 1, 116, 166, 210, 207, 218, 72, 110, 2, 17, 0, 0, 0, 8, 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