Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d031ac23e4b5246de90c57560a0627805fbd734c1974792b856c01f82c5fa47

Tx prefix hash: 1c088415b8f68d1c463a56f5dc0881c0619cdd283f966e0eaa1c17106667ea4d
Tx public key: 4594d133efa9675cd3c6c2df8945cb70c7ebd7053139b377bd1c91080039206b
Timestamp: 1722494671 Timestamp [UCT]: 2024-08-01 06:44:31 Age [y:d:h:m:s]: 00:175:03:04:52
Block: 1078233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125245 RingCT/type: yes/0
Extra: 014594d133efa9675cd3c6c2df8945cb70c7ebd7053139b377bd1c91080039206b02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46a7e5d347c009a20d81f92d4f81db22b0cd59d3a66151f42ec7c2e976c288e2 0.600000000000 1550806 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": 1078243, "vin": [ { "gen": { "height": 1078233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46a7e5d347c009a20d81f92d4f81db22b0cd59d3a66151f42ec7c2e976c288e2" } } ], "extra": [ 1, 69, 148, 209, 51, 239, 169, 103, 92, 211, 198, 194, 223, 137, 69, 203, 112, 199, 235, 215, 5, 49, 57, 179, 119, 189, 28, 145, 8, 0, 57, 32, 107, 2, 17, 0, 0, 0, 10, 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