Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d67a2fa98a85f2b4fa4d4057df0ae5dd72796da4d051f838c481bbea7e6916ca

Tx prefix hash: 164b2eb9f68f68678c771f3dd11fba9134d28e459e6059cc98dd108fb055ff4c
Tx public key: 6d2135728d3547a8ed6697ff4e8c62c0cb5e21ee724879edaf34942df89a3c1c
Timestamp: 1736574926 Timestamp [UCT]: 2025-01-11 05:55:26 Age [y:d:h:m:s]: 00:115:10:52:28
Block: 1194832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82313 RingCT/type: yes/0
Extra: 016d2135728d3547a8ed6697ff4e8c62c0cb5e21ee724879edaf34942df89a3c1c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04da26e34158e0cfa9045702f7e7f42ffc8c81c7299df8ca4426a70770c3275e 0.600000000000 1681409 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": 1194842, "vin": [ { "gen": { "height": 1194832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04da26e34158e0cfa9045702f7e7f42ffc8c81c7299df8ca4426a70770c3275e" } } ], "extra": [ 1, 109, 33, 53, 114, 141, 53, 71, 168, 237, 102, 151, 255, 78, 140, 98, 192, 203, 94, 33, 238, 114, 72, 121, 237, 175, 52, 148, 45, 248, 154, 60, 28, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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