Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f003fa56047c0e873cce7aac87debeef1c799e146db060fd530066d728ea531e

Tx prefix hash: 3394feefe8bb83b37a76261835be5a882c193e39e64764e52c2ed40459783835
Tx public key: b025354d0a5883f1dacdd59cdc15ec1d0c35d610fed53dc861f76e7c59af1f93
Timestamp: 1704755748 Timestamp [UCT]: 2024-01-08 23:15:48 Age [y:d:h:m:s]: 01:092:15:42:51
Block: 931157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327335 RingCT/type: yes/0
Extra: 01b025354d0a5883f1dacdd59cdc15ec1d0c35d610fed53dc861f76e7c59af1f9302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af3885b85c4fe05f331e2c1a23b0640176535af6fba79f0fdc57d3d29988e9f1 0.600000000000 1389049 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": 931167, "vin": [ { "gen": { "height": 931157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af3885b85c4fe05f331e2c1a23b0640176535af6fba79f0fdc57d3d29988e9f1" } } ], "extra": [ 1, 176, 37, 53, 77, 10, 88, 131, 241, 218, 205, 213, 156, 220, 21, 236, 29, 12, 53, 214, 16, 254, 213, 61, 200, 97, 247, 110, 124, 89, 175, 31, 147, 2, 17, 0, 0, 0, 1, 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