Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5d613ce3352b1f2da6382d5a6f4f83933ff52d1c8f565c3c1fcd12939f19aa

Tx prefix hash: 7d1e640c9cd53082a872e816b3775349c671eece952d6644d69ec01192d8ffea
Tx public key: 8f8849a637ce58e80b1f013336162fcd6c46a261f5e50e1eab23e9b56c5aa6c6
Timestamp: 1723291833 Timestamp [UCT]: 2024-08-10 12:10:33 Age [y:d:h:m:s]: 01:090:20:31:40
Block: 1084851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323397 RingCT/type: yes/0
Extra: 018f8849a637ce58e80b1f013336162fcd6c46a261f5e50e1eab23e9b56c5aa6c6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 910377d3803c861f63ebc652bfa2b59adca70d65b74b2d2d184aeeced82f578c 0.600000000000 1559274 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": 1084861, "vin": [ { "gen": { "height": 1084851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "910377d3803c861f63ebc652bfa2b59adca70d65b74b2d2d184aeeced82f578c" } } ], "extra": [ 1, 143, 136, 73, 166, 55, 206, 88, 232, 11, 31, 1, 51, 54, 22, 47, 205, 108, 70, 162, 97, 245, 229, 14, 30, 171, 35, 233, 181, 108, 90, 166, 198, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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