Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdff4648d2c532b4837d04c937c28b3a0866dd5bf8091d19c5fa43c228272d0

Tx prefix hash: 1d26045cf9d5af7414d83510dfa984b20db3b971e6a5f2d8ae6ddb702a99bbc2
Tx public key: 035bbfadfe3bfa9fc90f23b884af6f7601068a1be70f7bda62fa1f0936ad9793
Timestamp: 1734017702 Timestamp [UCT]: 2024-12-12 15:35:02 Age [y:d:h:m:s]: 00:121:13:48:01
Block: 1173682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86669 RingCT/type: yes/0
Extra: 01035bbfadfe3bfa9fc90f23b884af6f7601068a1be70f7bda62fa1f0936ad9793021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a21eba76bc0ececa205ae222efa0717b218c791e919b2c61de52d7196b4f0946 0.600000000000 1659731 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": 1173692, "vin": [ { "gen": { "height": 1173682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a21eba76bc0ececa205ae222efa0717b218c791e919b2c61de52d7196b4f0946" } } ], "extra": [ 1, 3, 91, 191, 173, 254, 59, 250, 159, 201, 15, 35, 184, 132, 175, 111, 118, 1, 6, 138, 27, 231, 15, 123, 218, 98, 250, 31, 9, 54, 173, 151, 147, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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