Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dff93324ec0ce73f376cd81f59755af3a1d28f3fb17489208401c674b36e046

Tx prefix hash: 9e252300fdbadd065839bdd4b8f8a24f498d7bd579699573d6da6da59c7ae312
Tx public key: 7908f9f5ba8d3ddbd135b622b4c8eabfaf1c70f2dd1fef33f73d543b45ca9266
Timestamp: 1730087597 Timestamp [UCT]: 2024-10-28 03:53:17 Age [y:d:h:m:s]: 00:157:16:35:41
Block: 1141108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112532 RingCT/type: yes/0
Extra: 017908f9f5ba8d3ddbd135b622b4c8eabfaf1c70f2dd1fef33f73d543b45ca926602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12bb07cf03d2860de1c66dce749a3f7f56bdde08632515638041e8c68acb5c11 0.600000000000 1624915 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": 1141118, "vin": [ { "gen": { "height": 1141108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12bb07cf03d2860de1c66dce749a3f7f56bdde08632515638041e8c68acb5c11" } } ], "extra": [ 1, 121, 8, 249, 245, 186, 141, 61, 219, 209, 53, 182, 34, 180, 200, 234, 191, 175, 28, 112, 242, 221, 31, 239, 51, 247, 61, 84, 59, 69, 202, 146, 102, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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