Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffb4bbd31761c15e668d6100f06cf8d744bb37ebf22bc7780af68c5bec606f7

Tx prefix hash: 0167124f7ece39a1f31a4b6b7c6c276f6dfc6a4012b2dc87cbe51e7d5dfcf79c
Tx public key: f28a242787bca25e44a7731f80209787b363f0ea07faa5df2165ff11413e18e1
Timestamp: 1697251244 Timestamp [UCT]: 2023-10-14 02:40:44 Age [y:d:h:m:s]: 02:025:22:32:05
Block: 869162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538160 RingCT/type: yes/0
Extra: 01f28a242787bca25e44a7731f80209787b363f0ea07faa5df2165ff11413e18e1021100000001e08532b6000000000000000000

1 output(s) for total of 0.809292501000 dcy

stealth address amount amount idx
00: c7ce4ab6ddabb9027049300019a90dbe08380a2c7918792b9e05bf4c5d2e477b 0.809292501000 1323997 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": 869172, "vin": [ { "gen": { "height": 869162 } } ], "vout": [ { "amount": 809292501, "target": { "key": "c7ce4ab6ddabb9027049300019a90dbe08380a2c7918792b9e05bf4c5d2e477b" } } ], "extra": [ 1, 242, 138, 36, 39, 135, 188, 162, 94, 68, 167, 115, 31, 128, 32, 151, 135, 179, 99, 240, 234, 7, 250, 165, 223, 33, 101, 255, 17, 65, 62, 24, 225, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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