Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 888e219ccc9aeec2d129f24d1d4b3a29c0560dda4fc18a40d2b749636594a8a6

Tx prefix hash: ee71c51dc23058a193f64f8ad68a5b3e5b3a2476f44ac01b3a95cb96a8ed1b2c
Tx public key: 741d4a1fefcb4a9de079bef80d05113e7695d77d031e110f027bbf7ba7c26f48
Timestamp: 1681508393 Timestamp [UCT]: 2023-04-14 21:39:53 Age [y:d:h:m:s]: 01:271:16:01:30
Block: 738678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455667 RingCT/type: yes/0
Extra: 01741d4a1fefcb4a9de079bef80d05113e7695d77d031e110f027bbf7ba7c26f48021100000003b3164c24000000000000000000

1 output(s) for total of 2.190046650000 dcy

stealth address amount amount idx
00: a0edfdd31654c0698554753d046e69f8cb57383d4e494c0461d73989e08694a8 2.190046650000 1185415 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": 738688, "vin": [ { "gen": { "height": 738678 } } ], "vout": [ { "amount": 2190046650, "target": { "key": "a0edfdd31654c0698554753d046e69f8cb57383d4e494c0461d73989e08694a8" } } ], "extra": [ 1, 116, 29, 74, 31, 239, 203, 74, 157, 224, 121, 190, 248, 13, 5, 17, 62, 118, 149, 215, 125, 3, 30, 17, 15, 2, 123, 191, 123, 167, 194, 111, 72, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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