Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29dd5424eb92f36dce1a7657f1d4cef3117c515da2adc2cc450a817054604579

Tx prefix hash: 5d19466c65a29494ea92448e55bce85f2d6950b0356f0b1cd543570ccee05ef8
Tx public key: 94807902a9f872ec6fd0b099c7a913e04dc3aa353d02375177c851d9f2115220
Timestamp: 1736140091 Timestamp [UCT]: 2025-01-06 05:08:11 Age [y:d:h:m:s]: 00:163:09:02:49
Block: 1191244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116452 RingCT/type: yes/0
Extra: 0194807902a9f872ec6fd0b099c7a913e04dc3aa353d02375177c851d9f21152200211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05447f507cd46687d0a9ebbbb1038c1a26873cd6f3a1d508969c17fb0c7f1aa4 0.600000000000 1677767 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": 1191254, "vin": [ { "gen": { "height": 1191244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05447f507cd46687d0a9ebbbb1038c1a26873cd6f3a1d508969c17fb0c7f1aa4" } } ], "extra": [ 1, 148, 128, 121, 2, 169, 248, 114, 236, 111, 208, 176, 153, 199, 169, 19, 224, 77, 195, 170, 53, 61, 2, 55, 81, 119, 200, 81, 217, 242, 17, 82, 32, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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