Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4e6c40e0c4e599f6be9b1c3939d7d770d900b27da9af3734d673716a978e616

Tx prefix hash: d825a3e1bfc8916ede1d136d4fbfd18137c03f99f305f13a693daa1160d0d33b
Tx public key: a13194e969d4be1cc63e020321eafd4c4ccb798053fca340626ffa6fb71fb9ed
Timestamp: 1717157767 Timestamp [UCT]: 2024-05-31 12:16:07 Age [y:d:h:m:s]: 00:306:17:32:35
Block: 1033990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219207 RingCT/type: yes/0
Extra: 01a13194e969d4be1cc63e020321eafd4c4ccb798053fca340626ffa6fb71fb9ed0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe5e91836bb2e7d7a99434f6c69d4220fba612325108848f23fb8179f25e8838 0.600000000000 1502463 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": 1034000, "vin": [ { "gen": { "height": 1033990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe5e91836bb2e7d7a99434f6c69d4220fba612325108848f23fb8179f25e8838" } } ], "extra": [ 1, 161, 49, 148, 233, 105, 212, 190, 28, 198, 62, 2, 3, 33, 234, 253, 76, 76, 203, 121, 128, 83, 252, 163, 64, 98, 111, 250, 111, 183, 31, 185, 237, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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