Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ea2bb4571f7d059ec04180c1b0e54db85ac038b78d3eaffd54a4958490440c

Tx prefix hash: 3641a539aa28a8bb0ee54c0f194bcf21b3a2e2c1ce7e540d9d60dbefa66a28f7
Tx public key: f673f2168a6a1b6f8173a779c4c026f8038e4aca51a7c7dd94c15b3d1f86433f
Timestamp: 1726490253 Timestamp [UCT]: 2024-09-16 12:37:33 Age [y:d:h:m:s]: 00:069:05:26:43
Block: 1111364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49486 RingCT/type: yes/0
Extra: 01f673f2168a6a1b6f8173a779c4c026f8038e4aca51a7c7dd94c15b3d1f86433f021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca7d1341eb95e561428b07d6cb463e7c1601b80f4a054bcc71a231f92a59db6f 0.600000000000 1590295 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": 1111374, "vin": [ { "gen": { "height": 1111364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca7d1341eb95e561428b07d6cb463e7c1601b80f4a054bcc71a231f92a59db6f" } } ], "extra": [ 1, 246, 115, 242, 22, 138, 106, 27, 111, 129, 115, 167, 121, 196, 192, 38, 248, 3, 142, 74, 202, 81, 167, 199, 221, 148, 193, 91, 61, 31, 134, 67, 63, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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