Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e20573f306b424709bc348074f8ce20f576900761937f356f5a0aeaed18ebe7

Tx prefix hash: 20ca9f692c01129b08a24603e5016a1baa003aad648de2ccff6a0ba1a21372b5
Tx public key: 611c72245c6b9c937f7483f9c6e4bef3cf1eb5d95ee7974724a72a9503bd8f62
Timestamp: 1695933187 Timestamp [UCT]: 2023-09-28 20:33:07 Age [y:d:h:m:s]: 01:261:16:27:49
Block: 858230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448021 RingCT/type: yes/0
Extra: 01611c72245c6b9c937f7483f9c6e4bef3cf1eb5d95ee7974724a72a9503bd8f62021100000005faf35c9c000000000000000000

1 output(s) for total of 0.879686215000 dcy

stealth address amount amount idx
00: e94eab4f6c81f4fdb34e1b0566faa7a6f1f0c2a0f87f823dae35e0e21111aa18 0.879686215000 1312396 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": 858240, "vin": [ { "gen": { "height": 858230 } } ], "vout": [ { "amount": 879686215, "target": { "key": "e94eab4f6c81f4fdb34e1b0566faa7a6f1f0c2a0f87f823dae35e0e21111aa18" } } ], "extra": [ 1, 97, 28, 114, 36, 92, 107, 156, 147, 127, 116, 131, 249, 198, 228, 190, 243, 207, 30, 181, 217, 94, 231, 151, 71, 36, 167, 42, 149, 3, 189, 143, 98, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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