Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f3385630f4adf51cb4adea9c4f6764ae4db6f4521ef2036366fdb25a412aceb

Tx prefix hash: 272655c63c1c8450d6f2181fcc125ebd762e8e9c76eb1da51ad8b4e93a4ba16a
Tx public key: 0455cde9f66964098f3327e8e014bd4b353049f815ffb16cd6aa076b00c92188
Timestamp: 1698669892 Timestamp [UCT]: 2023-10-30 12:44:52 Age [y:d:h:m:s]: 01:137:22:17:32
Block: 880936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359569 RingCT/type: yes/0
Extra: 010455cde9f66964098f3327e8e014bd4b353049f815ffb16cd6aa076b00c92188021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.739764267000 dcy

stealth address amount amount idx
00: efaedadf3823a76873c997724421ca3e5267d595fa2bc5cfff28786a1f9ac766 0.739764267000 1336506 of 0

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": 880946, "vin": [ { "gen": { "height": 880936 } } ], "vout": [ { "amount": 739764267, "target": { "key": "efaedadf3823a76873c997724421ca3e5267d595fa2bc5cfff28786a1f9ac766" } } ], "extra": [ 1, 4, 85, 205, 233, 246, 105, 100, 9, 143, 51, 39, 232, 224, 20, 189, 75, 53, 48, 73, 248, 21, 255, 177, 108, 214, 170, 7, 107, 0, 201, 33, 136, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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