Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18420f4ab3c1e00b8bdd3b915ef7e41651d05e6362b0310495df87f4a8d3f1c

Tx prefix hash: b3cc69da904bcd06008905c9512509a1554bd2cff53396a5695340d9532597fe
Tx public key: bfaf25f304aa535bab854317a42f2ebc02b595f2c191046ab18a05949d914eeb
Timestamp: 1714323752 Timestamp [UCT]: 2024-04-28 17:02:32 Age [y:d:h:m:s]: 01:192:00:59:11
Block: 1010487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395887 RingCT/type: yes/0
Extra: 01bfaf25f304aa535bab854317a42f2ebc02b595f2c191046ab18a05949d914eeb02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1ac5f76be4457f7d240b2893ce27c6eb2a604b8a9b9b4028fb2137eb2161c6c 0.600000000000 1472461 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": 1010497, "vin": [ { "gen": { "height": 1010487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1ac5f76be4457f7d240b2893ce27c6eb2a604b8a9b9b4028fb2137eb2161c6c" } } ], "extra": [ 1, 191, 175, 37, 243, 4, 170, 83, 91, 171, 133, 67, 23, 164, 47, 46, 188, 2, 181, 149, 242, 193, 145, 4, 106, 177, 138, 5, 148, 157, 145, 78, 235, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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