Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0217b49135dec9958926bd820abaccb32a80fc799496ae4d45b5049768c7994a

Tx prefix hash: 5103dc742844156ea42bf2e3acaa2f232b9e98fdc034907bb1baa3c318e1abc1
Tx public key: 1d3fa135fd944315d4da76fb8c32e2b6b2816f75632a0bb51dc523458bfe4c45
Timestamp: 1722947529 Timestamp [UCT]: 2024-08-06 12:32:09 Age [y:d:h:m:s]: 00:305:14:50:15
Block: 1081990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218361 RingCT/type: yes/0
Extra: 011d3fa135fd944315d4da76fb8c32e2b6b2816f75632a0bb51dc523458bfe4c45021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7df5c6c940a4da8e3bfe52dfb8e98d32876bc681021fc824055ed9d29886178 0.600000000000 1555813 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": 1082000, "vin": [ { "gen": { "height": 1081990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7df5c6c940a4da8e3bfe52dfb8e98d32876bc681021fc824055ed9d29886178" } } ], "extra": [ 1, 29, 63, 161, 53, 253, 148, 67, 21, 212, 218, 118, 251, 140, 50, 226, 182, 178, 129, 111, 117, 99, 42, 11, 181, 29, 197, 35, 69, 139, 254, 76, 69, 2, 17, 0, 0, 0, 5, 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