Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ef4b4d4825d7ef6712c8b30c2aa88ddbf0f06f917fbce8eaaabc240ce2091b

Tx prefix hash: 6bae0e810e8dfd36b56f2f8e4aa043b0fac6fd8084cf42f15c2b117df95ba374
Tx public key: 48b06e18e87d3b2be8556223fdf015a8ff77b72646ae5d70de9f2c0d4114b2ab
Timestamp: 1708477373 Timestamp [UCT]: 2024-02-21 01:02:53 Age [y:d:h:m:s]: 01:092:21:41:13
Block: 962020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327468 RingCT/type: yes/0
Extra: 0148b06e18e87d3b2be8556223fdf015a8ff77b72646ae5d70de9f2c0d4114b2ab0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28c9a1c8c7c3249661f682e6568fce0fa30427d995ca6bf5077b653afb9b95c5 0.600000000000 1421643 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": 962030, "vin": [ { "gen": { "height": 962020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28c9a1c8c7c3249661f682e6568fce0fa30427d995ca6bf5077b653afb9b95c5" } } ], "extra": [ 1, 72, 176, 110, 24, 232, 125, 59, 43, 232, 85, 98, 35, 253, 240, 21, 168, 255, 119, 183, 38, 70, 174, 93, 112, 222, 159, 44, 13, 65, 20, 178, 171, 2, 17, 0, 0, 0, 5, 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