Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1557954278e82fc4a52efa204ff82b531d0d63f1094f16394415c30d151de8c

Tx prefix hash: 961f093b7d7ee219de41f3bb0c219af582416e5cbc5756f72b92f10be469f740
Tx public key: 6f8dfadeaa970dd48529b3784e26a6d8e8fcfea088a086a3eb291df7a8ae19bd
Timestamp: 1578164705 Timestamp [UCT]: 2020-01-04 19:05:05 Age [y:d:h:m:s]: 04:317:10:33:31
Block: 38741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116020 RingCT/type: yes/0
Extra: 016f8dfadeaa970dd48529b3784e26a6d8e8fcfea088a086a3eb291df7a8ae19bd0211000000084ac5aa02000000000000000000

1 output(s) for total of 456.705071552000 dcy

stealth address amount amount idx
00: 222dd5c5e5a1f64f7f2305a0e02fe0cd700a70cc49f3046eac0239170ecb7d86 456.705071552000 66267 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": 38751, "vin": [ { "gen": { "height": 38741 } } ], "vout": [ { "amount": 456705071552, "target": { "key": "222dd5c5e5a1f64f7f2305a0e02fe0cd700a70cc49f3046eac0239170ecb7d86" } } ], "extra": [ 1, 111, 141, 250, 222, 170, 151, 13, 212, 133, 41, 179, 120, 78, 38, 166, 216, 232, 252, 254, 160, 136, 160, 134, 163, 235, 41, 29, 247, 168, 174, 25, 189, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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