Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1128d9f397a0af16401c8a48f9932225e57cd3f6e2b1a53581935473d847675

Tx prefix hash: bbc97ec1aaf16be57eb5eb5af705d77efee81684332a8ecdcdabe6bde67a0f39
Tx public key: 42d35bdf5342d9736e5e0e679bf1085d2e6b5c4433c9c1d39332b701d64a83d0
Timestamp: 1729340023 Timestamp [UCT]: 2024-10-19 12:13:43 Age [y:d:h:m:s]: 00:093:21:34:25
Block: 1134985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67069 RingCT/type: yes/0
Extra: 0142d35bdf5342d9736e5e0e679bf1085d2e6b5c4433c9c1d39332b701d64a83d0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5170510b2b089dc78970f2f2e7eff883fba5297159227909fcca42a02651e43 0.600000000000 1618312 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": 1134995, "vin": [ { "gen": { "height": 1134985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5170510b2b089dc78970f2f2e7eff883fba5297159227909fcca42a02651e43" } } ], "extra": [ 1, 66, 211, 91, 223, 83, 66, 217, 115, 110, 94, 14, 103, 155, 241, 8, 93, 46, 107, 92, 68, 51, 201, 193, 211, 147, 50, 183, 1, 214, 74, 131, 208, 2, 17, 0, 0, 0, 1, 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