Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7683ffe0251237436ddacb1dc8b8185183cfe99a47d3074f210b4c5255fce34d

Tx prefix hash: 52012d6521b451085142585f15e706e43b509b67801fba8359eb1b956de6e0f7
Tx public key: 0968ec066f283773c93e1f711520a8c20959f2d2e4589ee2cee62d78a980c716
Timestamp: 1703934090 Timestamp [UCT]: 2023-12-30 11:01:30 Age [y:d:h:m:s]: 01:117:04:39:03
Block: 924354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344890 RingCT/type: yes/0
Extra: 010968ec066f283773c93e1f711520a8c20959f2d2e4589ee2cee62d78a980c716021100000003ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db6da676602477f1fc775af2ebe35a34eb9c9c835ba732c8fee2be53283b3d9 0.600000000000 1382100 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": 924364, "vin": [ { "gen": { "height": 924354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db6da676602477f1fc775af2ebe35a34eb9c9c835ba732c8fee2be53283b3d9" } } ], "extra": [ 1, 9, 104, 236, 6, 111, 40, 55, 115, 201, 62, 31, 113, 21, 32, 168, 194, 9, 89, 242, 210, 228, 88, 158, 226, 206, 230, 45, 120, 169, 128, 199, 22, 2, 17, 0, 0, 0, 3, 172, 50, 141, 17, 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