Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1335f324bf4d632d5ca5a4aa0d7b2e99bc5256956b05d107e06ad9825f2dc4e2

Tx prefix hash: 81b514f8fbab760b91fdbbda65bd195b7036c99e968403b3ccd2f7ef38879aff
Tx public key: 99f7c9e9e78107a981afa7a0994ab949a980a8e4453cbc5897fb8ca02e53667e
Timestamp: 1715591810 Timestamp [UCT]: 2024-05-13 09:16:50 Age [y:d:h:m:s]: 00:287:22:05:40
Block: 1021029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205745 RingCT/type: yes/0
Extra: 0199f7c9e9e78107a981afa7a0994ab949a980a8e4453cbc5897fb8ca02e53667e021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0e90c03203cb42854d3d75cb92f6f6811b250fdd4b6a68f24a12a094ee78fb2 0.600000000000 1485198 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": 1021039, "vin": [ { "gen": { "height": 1021029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0e90c03203cb42854d3d75cb92f6f6811b250fdd4b6a68f24a12a094ee78fb2" } } ], "extra": [ 1, 153, 247, 201, 233, 231, 129, 7, 169, 129, 175, 167, 160, 153, 74, 185, 73, 169, 128, 168, 228, 69, 60, 188, 88, 151, 251, 140, 160, 46, 83, 102, 126, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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