Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eeb19412eed895fb0b006fc921b76d4a7ca86de8c60865eda299766b18b3b35

Tx prefix hash: dae45f46250fc4bd23d3f17ce1ff469e014adc5da605512006876bfbc7dfc1d1
Tx public key: a49f54aaa74a345d3134e9a417241b5f8e6fb41028b0103a9c2c9bb7163de8bc
Timestamp: 1736502872 Timestamp [UCT]: 2025-01-10 09:54:32 Age [y:d:h:m:s]: 00:154:01:47:54
Block: 1194225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109888 RingCT/type: yes/0
Extra: 01a49f54aaa74a345d3134e9a417241b5f8e6fb41028b0103a9c2c9bb7163de8bc0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19cd099521477eadf7d3182225b8e9fbc0f9eb1ab481d4090a4a721b16a9f1d2 0.600000000000 1680792 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": 1194235, "vin": [ { "gen": { "height": 1194225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19cd099521477eadf7d3182225b8e9fbc0f9eb1ab481d4090a4a721b16a9f1d2" } } ], "extra": [ 1, 164, 159, 84, 170, 167, 74, 52, 93, 49, 52, 233, 164, 23, 36, 27, 95, 142, 111, 180, 16, 40, 176, 16, 58, 156, 44, 155, 183, 22, 61, 232, 188, 2, 17, 0, 0, 0, 6, 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