Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba947ec963e89b6f21862f04955c8ba04e92a636835adb39c18ab864cb06521

Tx prefix hash: e45b0558941b4a1d8e8f7e8e30db9d3c141673e930272742a00c4e357ea9fc9e
Tx public key: 9d31422e2fc65ca27a7ecf3e50d9a12e12c6e72fae8c948ac0b5a7a486114cea
Timestamp: 1711391061 Timestamp [UCT]: 2024-03-25 18:24:21 Age [y:d:h:m:s]: 01:023:11:22:32
Block: 986208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277729 RingCT/type: yes/0
Extra: 019d31422e2fc65ca27a7ecf3e50d9a12e12c6e72fae8c948ac0b5a7a486114cea02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8d79e587c23df46913f7787f38f6fd1bde95217441ff038e2cca5db2bc9d743 0.600000000000 1446435 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": 986218, "vin": [ { "gen": { "height": 986208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8d79e587c23df46913f7787f38f6fd1bde95217441ff038e2cca5db2bc9d743" } } ], "extra": [ 1, 157, 49, 66, 46, 47, 198, 92, 162, 122, 126, 207, 62, 80, 217, 161, 46, 18, 198, 231, 47, 174, 140, 148, 138, 192, 181, 167, 164, 134, 17, 76, 234, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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