Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3da7289363bd7a79457658fb95bbe3ea7882a84f929839b517fb4384327a0d3d

Tx prefix hash: b347c4cad2987bcf63ce5178014ccd49973fe28491ba4c60114ab54c5c09cf38
Tx public key: ae78276c0d0d81a48e64ed443b6f662459f04123b909e665dff2b51722dbb059
Timestamp: 1581246649 Timestamp [UCT]: 2020-02-09 11:10:49 Age [y:d:h:m:s]: 05:001:09:03:10
Block: 61271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153745 RingCT/type: yes/0
Extra: 01ae78276c0d0d81a48e64ed443b6f662459f04123b909e665dff2b51722dbb05902110000000dd81c26c0000000000000000000

1 output(s) for total of 384.584758134000 dcy

stealth address amount amount idx
00: 2e21fd1aabda987d26f743d19e2b18a7c674474a89f2dae317f33db3cbb2a9d5 384.584758134000 112912 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": 61281, "vin": [ { "gen": { "height": 61271 } } ], "vout": [ { "amount": 384584758134, "target": { "key": "2e21fd1aabda987d26f743d19e2b18a7c674474a89f2dae317f33db3cbb2a9d5" } } ], "extra": [ 1, 174, 120, 39, 108, 13, 13, 129, 164, 142, 100, 237, 68, 59, 111, 102, 36, 89, 240, 65, 35, 185, 9, 230, 101, 223, 242, 181, 23, 34, 219, 176, 89, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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