Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e114cabc4601925ebd420f4c65933da3ff0fad4a0ebe0556899483f18a24f5c

Tx prefix hash: 61355a697aec9f8e4baebd392ac1fb4563d387730f12b6d79176e6ec389b1e4f
Tx public key: 32e3fb7c5cec8290dd486b8a040186aeb6c301c3d90275f964dfcf7b6e48c130
Timestamp: 1704328595 Timestamp [UCT]: 2024-01-04 00:36:35 Age [y:d:h:m:s]: 01:163:10:48:47
Block: 927642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377859 RingCT/type: yes/0
Extra: 0132e3fb7c5cec8290dd486b8a040186aeb6c301c3d90275f964dfcf7b6e48c130021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 191679e8bf0bf28c869de07decf898d8c2424724fb5da7bfe4910514168a8e3e 0.600000000000 1385478 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": 927652, "vin": [ { "gen": { "height": 927642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "191679e8bf0bf28c869de07decf898d8c2424724fb5da7bfe4910514168a8e3e" } } ], "extra": [ 1, 50, 227, 251, 124, 92, 236, 130, 144, 221, 72, 107, 138, 4, 1, 134, 174, 182, 195, 1, 195, 217, 2, 117, 249, 100, 223, 207, 123, 110, 72, 193, 48, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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