Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d59c0d1e11432ba90088ea782f83f0fd8d6a3d2a1da8a73793996521ea642f1

Tx prefix hash: 177431b7474f6184af21b33e23bcf37f93f5fb0f57d13045259626e9743f2e3c
Tx public key: 3a4a0d86e0ccf5db0b77219536fccd19cf03fda6bc35f8d346e87863f60e1336
Timestamp: 1735156324 Timestamp [UCT]: 2024-12-25 19:52:04 Age [y:d:h:m:s]: 00:081:16:41:25
Block: 1183093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58178 RingCT/type: yes/0
Extra: 013a4a0d86e0ccf5db0b77219536fccd19cf03fda6bc35f8d346e87863f60e1336021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64671902bd085207d7598e5f56882924802695d7c1bac1b23dd005dbee148e44 0.600000000000 1669534 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": 1183103, "vin": [ { "gen": { "height": 1183093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64671902bd085207d7598e5f56882924802695d7c1bac1b23dd005dbee148e44" } } ], "extra": [ 1, 58, 74, 13, 134, 224, 204, 245, 219, 11, 119, 33, 149, 54, 252, 205, 25, 207, 3, 253, 166, 188, 53, 248, 211, 70, 232, 120, 99, 246, 14, 19, 54, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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