Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e23020de5c29b79dd32057f4a736b0e78e92d06e225cc024c84e09394a27511

Tx prefix hash: 5e693a3d594f6d8e3459d0d7957a65df11105d7113975e31e66fac001b5b4620
Tx public key: d18258ba8d072303a77387b28f42c3a1f8a7e2702a21231fa606a8c8e3953379
Timestamp: 1731411493 Timestamp [UCT]: 2024-11-12 11:38:13 Age [y:d:h:m:s]: 01:035:00:03:57
Block: 1152070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283474 RingCT/type: yes/0
Extra: 01d18258ba8d072303a77387b28f42c3a1f8a7e2702a21231fa606a8c8e3953379021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8819e40107a8c2e84d2f1a58bcd9fd65531bdfbdfd3bc5603522ad036130764c 0.600000000000 1637661 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": 1152080, "vin": [ { "gen": { "height": 1152070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8819e40107a8c2e84d2f1a58bcd9fd65531bdfbdfd3bc5603522ad036130764c" } } ], "extra": [ 1, 209, 130, 88, 186, 141, 7, 35, 3, 167, 115, 135, 178, 143, 66, 195, 161, 248, 167, 226, 112, 42, 33, 35, 31, 166, 6, 168, 200, 227, 149, 51, 121, 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