Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 853c85b6076c7d40320fa5356f4baffc58cd44474ace2c728a157b5e6ce9e4c4

Tx prefix hash: 53589de76862fed492249d6991b600750ee7406dacd137401cd03ebdc0975322
Tx public key: 0b6f97ad63d8bbb3a0cd45f5babb5acb923e3b77baa40dad581032ae102c259c
Timestamp: 1708170706 Timestamp [UCT]: 2024-02-17 11:51:46 Age [y:d:h:m:s]: 01:038:01:32:06
Block: 959485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288222 RingCT/type: yes/0
Extra: 010b6f97ad63d8bbb3a0cd45f5babb5acb923e3b77baa40dad581032ae102c259c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b77127b344b6f737c8c1aaf67b76fcddc170c3a96f3a48cb9f75d210c46f23e9 0.600000000000 1419022 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": 959495, "vin": [ { "gen": { "height": 959485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b77127b344b6f737c8c1aaf67b76fcddc170c3a96f3a48cb9f75d210c46f23e9" } } ], "extra": [ 1, 11, 111, 151, 173, 99, 216, 187, 179, 160, 205, 69, 245, 186, 187, 90, 203, 146, 62, 59, 119, 186, 164, 13, 173, 88, 16, 50, 174, 16, 44, 37, 156, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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