Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dec55551db6995cb80bb90cea0365c623739a40c7a6648cc8ab49c9d0c6422a1

Tx prefix hash: 8a400d1c197b209c82bb14e2cbb359005169d197e5e3cdef94d3cb25f5c8a687
Tx public key: d5e8e447cc35b55e10767ddfeef3f0ea39c52d28f20130cebed04d6a190fc92a
Timestamp: 1716031545 Timestamp [UCT]: 2024-05-18 11:25:45 Age [y:d:h:m:s]: 00:320:08:58:47
Block: 1024659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228980 RingCT/type: yes/0
Extra: 01d5e8e447cc35b55e10767ddfeef3f0ea39c52d28f20130cebed04d6a190fc92a02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: e2e6700e44fe2b37094559f1359cd2afb8dd1a1d42a53d5caa001ec150cb7c5c 0.615580000000 1490572 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": 1024669, "vin": [ { "gen": { "height": 1024659 } } ], "vout": [ { "amount": 615580000, "target": { "key": "e2e6700e44fe2b37094559f1359cd2afb8dd1a1d42a53d5caa001ec150cb7c5c" } } ], "extra": [ 1, 213, 232, 228, 71, 204, 53, 181, 94, 16, 118, 125, 223, 238, 243, 240, 234, 57, 197, 45, 40, 242, 1, 48, 206, 190, 208, 77, 106, 25, 15, 201, 42, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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