Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c9d0733a7ce4b6b3510b8ffb3af062419ccf6f8b6bf2ccb05a8f20f786f9405

Tx prefix hash: de46815ee4fb8ac183e7778913482e0df5631b4d67719f561cea0915d04cfe31
Tx public key: 99ba0027244064f15120d42f14f19dd46c501e3a27eadb1e0223bacb3f4b7280
Timestamp: 1715389264 Timestamp [UCT]: 2024-05-11 01:01:04 Age [y:d:h:m:s]: 01:002:10:00:37
Block: 1019351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262628 RingCT/type: yes/0
Extra: 0199ba0027244064f15120d42f14f19dd46c501e3a27eadb1e0223bacb3f4b7280021100000004679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0720b4b028c6ed33c1b1344a0ca21c5ac17badee8d1365349682f5aec7c631f9 0.600000000000 1483296 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": 1019361, "vin": [ { "gen": { "height": 1019351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0720b4b028c6ed33c1b1344a0ca21c5ac17badee8d1365349682f5aec7c631f9" } } ], "extra": [ 1, 153, 186, 0, 39, 36, 64, 100, 241, 81, 32, 212, 47, 20, 241, 157, 212, 108, 80, 30, 58, 39, 234, 219, 30, 2, 35, 186, 203, 63, 75, 114, 128, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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