Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a48e31ddbdd142ca73eee980bce2f8b998fd9156c75bf42c459be178a25b6b61

Tx prefix hash: 2b9a088430a31f413a9b9b09910e952f082332881e70c77c232f48d87b483f4d
Tx public key: 5126e131a7cb2814c5d7f0a0783278c010470ee62ac14dabda427d44ccc2a6a4
Timestamp: 1708221333 Timestamp [UCT]: 2024-02-18 01:55:33 Age [y:d:h:m:s]: 01:096:00:42:34
Block: 959898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329714 RingCT/type: yes/0
Extra: 015126e131a7cb2814c5d7f0a0783278c010470ee62ac14dabda427d44ccc2a6a40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72d5bf7d05757a4241e3f8cf89b766f63b9489ef6a4866ad3a5af19605d809fa 0.600000000000 1419457 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": 959908, "vin": [ { "gen": { "height": 959898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72d5bf7d05757a4241e3f8cf89b766f63b9489ef6a4866ad3a5af19605d809fa" } } ], "extra": [ 1, 81, 38, 225, 49, 167, 203, 40, 20, 197, 215, 240, 160, 120, 50, 120, 192, 16, 71, 14, 230, 42, 193, 77, 171, 218, 66, 125, 68, 204, 194, 166, 164, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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