Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e27573eae79e9ebbc1fff53de6546bc1685e6e8fc0f4f1b22f2f04ad112511d

Tx prefix hash: 1ea357e481567f461a542974460c895b21514075e5c61df873c6b7a7f298729f
Tx public key: 4204ed8c47a77c351f7273eed7503befaa4e48f6d4bfc3ecd7ea95ac885cbe32
Timestamp: 1694878560 Timestamp [UCT]: 2023-09-16 15:36:00 Age [y:d:h:m:s]: 02:066:10:09:24
Block: 849471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567150 RingCT/type: yes/0
Extra: 014204ed8c47a77c351f7273eed7503befaa4e48f6d4bfc3ecd7ea95ac885cbe3202110000000233af99f4000000000000000000

1 output(s) for total of 0.940480948000 dcy

stealth address amount amount idx
00: 13fc64c1e4f39118f4322d1d44800d53ab6a38f5816b071944ad52f3e1526f10 0.940480948000 1303137 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": 849481, "vin": [ { "gen": { "height": 849471 } } ], "vout": [ { "amount": 940480948, "target": { "key": "13fc64c1e4f39118f4322d1d44800d53ab6a38f5816b071944ad52f3e1526f10" } } ], "extra": [ 1, 66, 4, 237, 140, 71, 167, 124, 53, 31, 114, 115, 238, 215, 80, 59, 239, 170, 78, 72, 246, 212, 191, 195, 236, 215, 234, 149, 172, 136, 92, 190, 50, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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