Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94fe40147be05d4d7473e083cd6742d2aba30ed670f99118e391b6ecda2448da

Tx prefix hash: 7a2169dd90c37d12d4c79acadea6a30bcaf8b91a3053e3ea3962b28aa1305a41
Tx public key: c3670577d26626a0abb6b16222e0f0644bf79c7ab30e3105042648b92da2fcab
Timestamp: 1636888374 Timestamp [UCT]: 2021-11-14 11:12:54 Age [y:d:h:m:s]: 03:164:16:20:04
Block: 374130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 896184 RingCT/type: yes/0
Extra: 01c3670577d26626a0abb6b16222e0f0644bf79c7ab30e3105042648b92da2fcab0211000000024a0f5013000000000000000000

1 output(s) for total of 35.346986131000 dcy

stealth address amount amount idx
00: e61ab6c6101e35f73dca8b2b5a771cc4cb4c4daaced5e91d7043f2bf1fd908d2 35.346986131000 757394 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": 374140, "vin": [ { "gen": { "height": 374130 } } ], "vout": [ { "amount": 35346986131, "target": { "key": "e61ab6c6101e35f73dca8b2b5a771cc4cb4c4daaced5e91d7043f2bf1fd908d2" } } ], "extra": [ 1, 195, 103, 5, 119, 210, 102, 38, 160, 171, 182, 177, 98, 34, 224, 240, 100, 75, 247, 156, 122, 179, 14, 49, 5, 4, 38, 72, 185, 45, 162, 252, 171, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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