Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f531c40f410036da8253fbab859a2b875a23093e25ffa54d5424865bbda4d2e

Tx prefix hash: 032123f087b9270471bf39e2cf8333038428eb548784c43b704cb427b1939259
Tx public key: ab7bfd074a310d6df8bfa482fc16c7124fcf8b0bbd5953875f88175113083ac8
Timestamp: 1635286834 Timestamp [UCT]: 2021-10-26 22:20:34 Age [y:d:h:m:s]: 03:109:04:29:26
Block: 361131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 856228 RingCT/type: yes/0
Extra: 01ab7bfd074a310d6df8bfa482fc16c7124fcf8b0bbd5953875f88175113083ac80211000000806e80e2c6000000000000000000

1 output(s) for total of 39.032241455000 dcy

stealth address amount amount idx
00: 7ca3605694eabc159cd9e4bd9a3be02e2211f2c9c27518e1f3f3cc8d047ca322 39.032241455000 734832 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": 361141, "vin": [ { "gen": { "height": 361131 } } ], "vout": [ { "amount": 39032241455, "target": { "key": "7ca3605694eabc159cd9e4bd9a3be02e2211f2c9c27518e1f3f3cc8d047ca322" } } ], "extra": [ 1, 171, 123, 253, 7, 74, 49, 13, 109, 248, 191, 164, 130, 252, 22, 199, 18, 79, 207, 139, 11, 189, 89, 83, 135, 95, 136, 23, 81, 19, 8, 58, 200, 2, 17, 0, 0, 0, 128, 110, 128, 226, 198, 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