Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de133fc910dff895b07d6c2385794e5776fa91708a1fc1421cd8db74806a807f

Tx prefix hash: 860524f6921740f2c2b88459fe101510169b2e15a82cf784fd0967e63b46c6a0
Tx public key: e8f1fa72088d00260c781ca69e951640e85339bb24181f2d83e5b80269d5741c
Timestamp: 1680091419 Timestamp [UCT]: 2023-03-29 12:03:39 Age [y:d:h:m:s]: 01:334:03:29:33
Block: 727592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499434 RingCT/type: yes/0
Extra: 01e8f1fa72088d00260c781ca69e951640e85339bb24181f2d83e5b80269d5741c021100000002e7ace25d000000000000000000

1 output(s) for total of 2.383339453000 dcy

stealth address amount amount idx
00: a2d7d2fc236fa7d5dd2a3a8d3b112ead59ab0f92dfdd8f10b74e06d33eaf912a 2.383339453000 1172907 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": 727602, "vin": [ { "gen": { "height": 727592 } } ], "vout": [ { "amount": 2383339453, "target": { "key": "a2d7d2fc236fa7d5dd2a3a8d3b112ead59ab0f92dfdd8f10b74e06d33eaf912a" } } ], "extra": [ 1, 232, 241, 250, 114, 8, 141, 0, 38, 12, 120, 28, 166, 158, 149, 22, 64, 232, 83, 57, 187, 36, 24, 31, 45, 131, 229, 184, 2, 105, 213, 116, 28, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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