Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 178c556779b5aa63febf97263300bdf50dfa73e48ec98fab057f6d78e4b520d1

Tx prefix hash: 6160df5ab441d11dee860d491ab4d00520a1b94c11d13ef2313c9349309fdbf1
Tx public key: aa93d1aa79bbae0b0c765088656010a735e4dc1907cdc4b5559f096b41b49b5f
Timestamp: 1702378383 Timestamp [UCT]: 2023-12-12 10:53:03 Age [y:d:h:m:s]: 01:357:02:03:58
Block: 911477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514101 RingCT/type: yes/0
Extra: 01aa93d1aa79bbae0b0c765088656010a735e4dc1907cdc4b5559f096b41b49b5f02110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2a4689071adbea3e93614adac72c5b4352444511132d16045d1f1dd4b64923f 0.600000000000 1368681 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": 911487, "vin": [ { "gen": { "height": 911477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2a4689071adbea3e93614adac72c5b4352444511132d16045d1f1dd4b64923f" } } ], "extra": [ 1, 170, 147, 209, 170, 121, 187, 174, 11, 12, 118, 80, 136, 101, 96, 16, 167, 53, 228, 220, 25, 7, 205, 196, 181, 85, 159, 9, 107, 65, 180, 155, 95, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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