Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 698178a2eb728e720cdd8a76eb90c9865363ef262c8dccb082228ddbf3606673

Tx prefix hash: 5a0fc095ada81e2a7a20ed49a0812aafbf743e7be75a4677b1029d40fb30323e
Tx public key: 2468a0ebcdfa0ec937ab24445319b44bbdf59f54c1573d85308cc2f41f45f78b
Timestamp: 1661442564 Timestamp [UCT]: 2022-08-25 15:49:24 Age [y:d:h:m:s]: 03:101:16:29:57
Block: 573604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 852537 RingCT/type: yes/0
Extra: 012468a0ebcdfa0ec937ab24445319b44bbdf59f54c1573d85308cc2f41f45f78b02110000000475e3f0e9000000000000000000

1 output(s) for total of 7.716350233000 dcy

stealth address amount amount idx
00: 57aa670ac1377178283f7a7b115b073a5207d7870d766ec3ea0bfcf75e4a2296 7.716350233000 1006898 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": 573614, "vin": [ { "gen": { "height": 573604 } } ], "vout": [ { "amount": 7716350233, "target": { "key": "57aa670ac1377178283f7a7b115b073a5207d7870d766ec3ea0bfcf75e4a2296" } } ], "extra": [ 1, 36, 104, 160, 235, 205, 250, 14, 201, 55, 171, 36, 68, 83, 25, 180, 75, 189, 245, 159, 84, 193, 87, 61, 133, 48, 140, 194, 244, 31, 69, 247, 139, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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