Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d128d279a35cc52681b160f4c1fdc94c08c3fcea33f9784073417961a3dfa48f

Tx prefix hash: d78e304064c333406a1681e5b22c8b885dc47a38c976a211a44e1f74f3d76205
Tx public key: 388c6c97883fac9d811aeaa33986d8cadd63ffc96ca17a79a64cf5752517c7f0
Timestamp: 1722260331 Timestamp [UCT]: 2024-07-29 13:38:51 Age [y:d:h:m:s]: 00:233:08:31:46
Block: 1076297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166698 RingCT/type: yes/0
Extra: 01388c6c97883fac9d811aeaa33986d8cadd63ffc96ca17a79a64cf5752517c7f002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c612a1eaffa76efafe78a2fc5a4965919d385a43af1ffec9c6a2903804ffa9ac 0.600000000000 1548834 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": 1076307, "vin": [ { "gen": { "height": 1076297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c612a1eaffa76efafe78a2fc5a4965919d385a43af1ffec9c6a2903804ffa9ac" } } ], "extra": [ 1, 56, 140, 108, 151, 136, 63, 172, 157, 129, 26, 234, 163, 57, 134, 216, 202, 221, 99, 255, 201, 108, 161, 122, 121, 166, 76, 245, 117, 37, 23, 199, 240, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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