Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cddf28d029adaa4e009e42abbb4f089cf166cdc4d077f8f2dd8d9564bb753ec

Tx prefix hash: c0c81fb87bd19b77a3268368090c69d4d930781d2deae9f95bacb3bc471c691f
Tx public key: 74803d45feee0d0cbf7523b0b869401947165326ff56d309db258bae241d55f6
Timestamp: 1577677520 Timestamp [UTC]: 2019-12-30 03:45:20 Age [y:d:h:m:s]: 06:051:22:51:47
Block: 34761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1445284 RingCT/type: yes/0
Extra: 0174803d45feee0d0cbf7523b0b869401947165326ff56d309db258bae241d55f60211000000104ac5aa02000000000000000000

1 output(s) for total of 0.470785666990 xmr

stealth address amount amount idx tag
00: b439647b4cdf238f8fa70b2cb1c9a930903f932b00255d351b50bf3a9cf0fd2d 0.470785666990 58540 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 dinastycoin-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": 34771, "vin": [ { "gen": { "height": 34761 } } ], "vout": [ { "amount": 470785666990, "target": { "key": "b439647b4cdf238f8fa70b2cb1c9a930903f932b00255d351b50bf3a9cf0fd2d" } } ], "extra": [ 1, 116, 128, 61, 69, 254, 238, 13, 12, 191, 117, 35, 176, 184, 105, 64, 25, 71, 22, 83, 38, 255, 86, 211, 9, 219, 37, 139, 174, 36, 29, 85, 246, 2, 17, 0, 0, 0, 16, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369