Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96a86aa7487ba3bc067f6145bac6b452630963c4ac5e3d2c374e9895e4e1e90

Tx prefix hash: e878e947ae14237dfd172620d9208a63b3940777216e771fb9969a2c1179fef1
Tx public key: c2adfd9a897f91af2f1406802e79ab53bd4ed78a2c8b2c2caa3c64f5a24ca966
Timestamp: 1699436293 Timestamp [UCT]: 2023-11-08 09:38:13 Age [y:d:h:m:s]: 01:186:20:01:22
Block: 887070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394745 RingCT/type: yes/0
Extra: 01c2adfd9a897f91af2f1406802e79ab53bd4ed78a2c8b2c2caa3c64f5a24ca96602110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.705941725000 dcy

stealth address amount amount idx
00: fc99c71d89b04efc69ea1784fc86eee0aedbd5a1fa2742935b6e64094c742d98 0.705941725000 1342925 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": 887080, "vin": [ { "gen": { "height": 887070 } } ], "vout": [ { "amount": 705941725, "target": { "key": "fc99c71d89b04efc69ea1784fc86eee0aedbd5a1fa2742935b6e64094c742d98" } } ], "extra": [ 1, 194, 173, 253, 154, 137, 127, 145, 175, 47, 20, 6, 128, 46, 121, 171, 83, 189, 78, 215, 138, 44, 139, 44, 44, 170, 60, 100, 245, 162, 76, 169, 102, 2, 17, 0, 0, 0, 11, 250, 243, 92, 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