Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4cb6b1a6debf125f33af42e3e38345086553aee8af8b01522c4cdfa96991063

Tx prefix hash: a3a7098a0b068e52fc83979a4eba3e593759db6c8fe17e7786a05928ed3e75ee
Tx public key: bccc86dd8f31253bf2d74f9205795ab191102535489555c8f9efab5f688d6fb8
Timestamp: 1694766651 Timestamp [UCT]: 2023-09-15 08:30:51 Age [y:d:h:m:s]: 01:132:15:23:18
Block: 848540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356083 RingCT/type: yes/0
Extra: 01bccc86dd8f31253bf2d74f9205795ab191102535489555c8f9efab5f688d6fb8021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.947184959000 dcy

stealth address amount amount idx
00: c3c4fb03edc9f11580827864561a43949a295e3311ce924a9e6daca9db39a463 0.947184959000 1302150 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": 848550, "vin": [ { "gen": { "height": 848540 } } ], "vout": [ { "amount": 947184959, "target": { "key": "c3c4fb03edc9f11580827864561a43949a295e3311ce924a9e6daca9db39a463" } } ], "extra": [ 1, 188, 204, 134, 221, 143, 49, 37, 59, 242, 215, 79, 146, 5, 121, 90, 177, 145, 16, 37, 53, 72, 149, 85, 200, 249, 239, 171, 95, 104, 141, 111, 184, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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