Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec019b2a29064e27d49a96f75ba326681cca3d5dd10eefe2f7a5052775437659

Tx prefix hash: 90bae330fe948f348b28557733751c7bd01019cd098c92b4d84b63a76805a33f
Tx public key: 8468e42c16880ae5b9b02ef920c830d876238115f6dc4fff2a89a4e54bf14c30
Timestamp: 1702687336 Timestamp [UCT]: 2023-12-16 00:42:16 Age [y:d:h:m:s]: 01:138:10:50:19
Block: 914018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360107 RingCT/type: yes/0
Extra: 018468e42c16880ae5b9b02ef920c830d876238115f6dc4fff2a89a4e54bf14c30021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f452e9e1c7acbeaa7f5d33114bc8b78c7fcfb52f9f5996291000f15e3d280ef1 0.600000000000 1371298 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": 914028, "vin": [ { "gen": { "height": 914018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f452e9e1c7acbeaa7f5d33114bc8b78c7fcfb52f9f5996291000f15e3d280ef1" } } ], "extra": [ 1, 132, 104, 228, 44, 22, 136, 10, 229, 185, 176, 46, 249, 32, 200, 48, 216, 118, 35, 129, 21, 246, 220, 79, 255, 42, 137, 164, 229, 75, 241, 76, 48, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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