Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba2745d7f9eae93221a83d7664a40dee7245323b26ad08e93a890c15942d83c

Tx prefix hash: f40dea62f9e76ee0215de6cd6907935e6c3d26a881a595ae6bf3be7b44f0ca2e
Tx public key: b815e2162fcb66d70a5e03a9dce8d4a1119d7bd30684b3da9f65e5540a20dc08
Timestamp: 1704106586 Timestamp [UCT]: 2024-01-01 10:56:26 Age [y:d:h:m:s]: 01:322:04:31:32
Block: 925783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489111 RingCT/type: yes/0
Extra: 01b815e2162fcb66d70a5e03a9dce8d4a1119d7bd30684b3da9f65e5540a20dc0802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59beff542cfeeae8c661acc8b48014c02021dc044b796491264788084d177609 0.600000000000 1383551 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": 925793, "vin": [ { "gen": { "height": 925783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59beff542cfeeae8c661acc8b48014c02021dc044b796491264788084d177609" } } ], "extra": [ 1, 184, 21, 226, 22, 47, 203, 102, 215, 10, 94, 3, 169, 220, 232, 212, 161, 17, 157, 123, 211, 6, 132, 179, 218, 159, 101, 229, 84, 10, 32, 220, 8, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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