Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c09a3c352d2802dcd2c34cbf56d1bd454d62e2eee80b1f950187fb438bb0aa3

Tx prefix hash: 4f990d3af8ac8aaf9dfe069a5b11f3cb14b30f1f9ea90860720b64c5a2dedbf3
Tx public key: b924c8f50efad7ab159b55f08cb6c4e904c6c6179adbe66deeccae5f250cb0d6
Timestamp: 1704108079 Timestamp [UCT]: 2024-01-01 11:21:19 Age [y:d:h:m:s]: 01:100:07:31:48
Block: 925796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332809 RingCT/type: yes/0
Extra: 01b924c8f50efad7ab159b55f08cb6c4e904c6c6179adbe66deeccae5f250cb0d60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6340305f5f15829f27abda9b1bfba5a49d1c92bd9a6d79436588e126014bf5f 0.600000000000 1383564 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": 925806, "vin": [ { "gen": { "height": 925796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6340305f5f15829f27abda9b1bfba5a49d1c92bd9a6d79436588e126014bf5f" } } ], "extra": [ 1, 185, 36, 200, 245, 14, 250, 215, 171, 21, 155, 85, 240, 140, 182, 196, 233, 4, 198, 198, 23, 154, 219, 230, 109, 238, 204, 174, 95, 37, 12, 176, 214, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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