Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b561dc42f9234d6f8dd9c61b777844b18750f95ceb3b8389cc884c34044b6035

Tx prefix hash: 5d613d66e11aff1ed61e7a41e83f13927480d2da82dede45c433a5b4001d3a0a
Tx public key: d6ba163adbe39ee4d9f3b6a0381f15a2fe760d39086d1c26a3918028c9ec4eee
Timestamp: 1735383799 Timestamp [UCT]: 2024-12-28 11:03:19 Age [y:d:h:m:s]: 00:102:11:24:30
Block: 1184971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73019 RingCT/type: yes/0
Extra: 01d6ba163adbe39ee4d9f3b6a0381f15a2fe760d39086d1c26a3918028c9ec4eee0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 464da949da4a4a98c1f15ea58094b4996db7cd397af7a6f9049ecf87c2c36f94 0.600000000000 1671434 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": 1184981, "vin": [ { "gen": { "height": 1184971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "464da949da4a4a98c1f15ea58094b4996db7cd397af7a6f9049ecf87c2c36f94" } } ], "extra": [ 1, 214, 186, 22, 58, 219, 227, 158, 228, 217, 243, 182, 160, 56, 31, 21, 162, 254, 118, 13, 57, 8, 109, 28, 38, 163, 145, 128, 40, 201, 236, 78, 238, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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