Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0524e554ce07b0f31e1a86dacfa30ad85e1e6ca7e24fc3803f70f64e3412dcea

Tx prefix hash: 25ea879e864fc0eec546df9b63e168c12cbd5f19f25e95bd2ea34e02b71ce3ed
Tx public key: 54a52f9b53142ac5a7c26b567577a95fd34d92c1e5db742eecbd8e3664de7f4a
Timestamp: 1736165808 Timestamp [UCT]: 2025-01-06 12:16:48 Age [y:d:h:m:s]: 00:091:03:22:11
Block: 1191451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64906 RingCT/type: yes/0
Extra: 0154a52f9b53142ac5a7c26b567577a95fd34d92c1e5db742eecbd8e3664de7f4a0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1fbeb3f5bf05573e2c54aa17405b9b3398af5e06239fcd17c9ffc8b520b417e 0.600000000000 1677990 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": 1191461, "vin": [ { "gen": { "height": 1191451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1fbeb3f5bf05573e2c54aa17405b9b3398af5e06239fcd17c9ffc8b520b417e" } } ], "extra": [ 1, 84, 165, 47, 155, 83, 20, 42, 197, 167, 194, 107, 86, 117, 119, 169, 95, 211, 77, 146, 193, 229, 219, 116, 46, 236, 189, 142, 54, 100, 222, 127, 74, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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