Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b38db638a7cf26d999e68ba0ca0f6c4051ec38435e0797130f64a61a024a2aae

Tx prefix hash: 933ca7c1795f24817ee7dadda6c045d69e84b8b9974975897adb61f32c44b5f3
Tx public key: 929c070c5318bee93c675f0599e2f561033d032e6f0315f6b7a3baebc6fb3473
Timestamp: 1580790075 Timestamp [UCT]: 2020-02-04 04:21:15 Age [y:d:h:m:s]: 05:039:23:54:39
Block: 58249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180624 RingCT/type: yes/0
Extra: 01929c070c5318bee93c675f0599e2f561033d032e6f0315f6b7a3baebc6fb34730211000000048a2ee0d9000000000000000000

1 output(s) for total of 393.567774491000 dcy

stealth address amount amount idx
00: 59344629a49e7dd4f8d23dc2f3cd5692c7d864248c1cfc9be3b95d40d19e30ab 393.567774491000 107655 of 0

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": 58259, "vin": [ { "gen": { "height": 58249 } } ], "vout": [ { "amount": 393567774491, "target": { "key": "59344629a49e7dd4f8d23dc2f3cd5692c7d864248c1cfc9be3b95d40d19e30ab" } } ], "extra": [ 1, 146, 156, 7, 12, 83, 24, 190, 233, 60, 103, 95, 5, 153, 226, 245, 97, 3, 61, 3, 46, 111, 3, 21, 246, 183, 163, 186, 235, 198, 251, 52, 115, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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