Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90f71a8eeff4aa148ccf264e75f011c01690bb8c23575e4b0841e9c3c1f53238

Tx prefix hash: d1c2a43b7e1468d1f6461049c886bf94160cb00f614f0785b1e560cad024a434
Tx public key: 20ec1509fd2e2d5b80d540c3aabf25ef45ae0be6a965ba1dff2cb8096133b3d4
Timestamp: 1709879488 Timestamp [UCT]: 2024-03-08 06:31:28 Age [y:d:h:m:s]: 01:053:14:17:54
Block: 973657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299304 RingCT/type: yes/0
Extra: 0120ec1509fd2e2d5b80d540c3aabf25ef45ae0be6a965ba1dff2cb8096133b3d40211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56df04d966997ff82d6a21b87de67504251495d84c426191b0ca35fc9ecd4ecb 0.600000000000 1433592 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": 973667, "vin": [ { "gen": { "height": 973657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56df04d966997ff82d6a21b87de67504251495d84c426191b0ca35fc9ecd4ecb" } } ], "extra": [ 1, 32, 236, 21, 9, 253, 46, 45, 91, 128, 213, 64, 195, 170, 191, 37, 239, 69, 174, 11, 230, 169, 101, 186, 29, 255, 44, 184, 9, 97, 51, 179, 212, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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