Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09f024c6416c83c76d67e6f63047b18e8094bc47c5f2fb75eae4b0afff20ac93

Tx prefix hash: bed848536b40340bfc475605e8b201501c67f2e4ee311d7603836dd2f2d7a8a8
Tx public key: 7f87d425a8e0424f514051ac5092c16063cd91ed5c1b66b572f7023e0d3a2b05
Timestamp: 1703584042 Timestamp [UCT]: 2023-12-26 09:47:22 Age [y:d:h:m:s]: 01:321:09:54:54
Block: 921456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488557 RingCT/type: yes/0
Extra: 017f87d425a8e0424f514051ac5092c16063cd91ed5c1b66b572f7023e0d3a2b0502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eab3459bf94849e751dcdddb8fad5fcf987cf580f63cb8ac0f4555085644c46c 0.600000000000 1379144 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": 921466, "vin": [ { "gen": { "height": 921456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eab3459bf94849e751dcdddb8fad5fcf987cf580f63cb8ac0f4555085644c46c" } } ], "extra": [ 1, 127, 135, 212, 37, 168, 224, 66, 79, 81, 64, 81, 172, 80, 146, 193, 96, 99, 205, 145, 237, 92, 27, 102, 181, 114, 247, 2, 62, 13, 58, 43, 5, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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