Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2978252f23f6d3416fb42389734c9c68a004d8582de303365cb34433779130ae

Tx prefix hash: 5107647153a39284e5228c79d0aa52b127458fd675e32e25c3ed888f2d5e83ee
Tx public key: f94ee9226a027977cb1a3e561d0566e34b75c508ea32b0c02705bc3448a45037
Timestamp: 1609175803 Timestamp [UCT]: 2020-12-28 17:16:43 Age [y:d:h:m:s]: 03:363:15:20:22
Block: 170959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1012512 RingCT/type: yes/0
Extra: 01f94ee9226a027977cb1a3e561d0566e34b75c508ea32b0c02705bc3448a45037021100000160aad74b3a000000000000000000

1 output(s) for total of 166.549191554000 dcy

stealth address amount amount idx
00: 34455a7217576c5af3c017b2e4f64c4ef6bf0b105a7a8ee2881d2f65a8ddbd11 166.549191554000 321298 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": 170969, "vin": [ { "gen": { "height": 170959 } } ], "vout": [ { "amount": 166549191554, "target": { "key": "34455a7217576c5af3c017b2e4f64c4ef6bf0b105a7a8ee2881d2f65a8ddbd11" } } ], "extra": [ 1, 249, 78, 233, 34, 106, 2, 121, 119, 203, 26, 62, 86, 29, 5, 102, 227, 75, 117, 197, 8, 234, 50, 176, 192, 39, 5, 188, 52, 72, 164, 80, 55, 2, 17, 0, 0, 1, 96, 170, 215, 75, 58, 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