Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f207b3c8b4384653b2dfe72cb80e80019a87640890b62979dccbfab87e339f

Tx prefix hash: d8bc893ca34dcbd518914f074a8d929cbe9caf2e8f72ad20a6c21ff25b4a68a4
Tx public key: 76a8f83a6c9cc9cd3d99a96540c610b43700c0ef40401c2d1603887f84459428
Timestamp: 1736631849 Timestamp [UCT]: 2025-01-11 21:44:09 Age [y:d:h:m:s]: 00:068:20:14:01
Block: 1195296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48983 RingCT/type: yes/0
Extra: 0176a8f83a6c9cc9cd3d99a96540c610b43700c0ef40401c2d1603887f844594280211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8af8cd9f50fab998e95352894c0967a581c67a11253ae5a0115161f6deb1aa10 0.600000000000 1681885 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": 1195306, "vin": [ { "gen": { "height": 1195296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8af8cd9f50fab998e95352894c0967a581c67a11253ae5a0115161f6deb1aa10" } } ], "extra": [ 1, 118, 168, 248, 58, 108, 156, 201, 205, 61, 153, 169, 101, 64, 198, 16, 180, 55, 0, 192, 239, 64, 64, 28, 45, 22, 3, 136, 127, 132, 69, 148, 40, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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