Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58321d8c35e5b438e19afba1a564781199f342dfa5b604d712c703e0b3c9a024

Tx prefix hash: 99431857b7e80fe2c3679f9c4d2a07bdba08c9444c8c52c9eeb0b462cfb4a1d0
Tx public key: ebf809f89b160c831d388464a633b29b0af16d73995472dc11a99787b9299753
Timestamp: 1729632034 Timestamp [UCT]: 2024-10-22 21:20:34 Age [y:d:h:m:s]: 00:142:09:54:02
Block: 1137376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101582 RingCT/type: yes/0
Extra: 01ebf809f89b160c831d388464a633b29b0af16d73995472dc11a99787b929975302110000000192627dee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b83005432d2f26922e2c7639c4113ea7ddce3364820398def9e014e5d215c9f7 0.600000000000 1620855 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": 1137386, "vin": [ { "gen": { "height": 1137376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b83005432d2f26922e2c7639c4113ea7ddce3364820398def9e014e5d215c9f7" } } ], "extra": [ 1, 235, 248, 9, 248, 155, 22, 12, 131, 29, 56, 132, 100, 166, 51, 178, 155, 10, 241, 109, 115, 153, 84, 114, 220, 17, 169, 151, 135, 185, 41, 151, 83, 2, 17, 0, 0, 0, 1, 146, 98, 125, 238, 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