Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f0aad2693be4efe8c78f2af4279d04279dc87fa4f97281b2b89d4f561a1063

Tx prefix hash: 6bb7066558c26f786a10df5fea0af7836195df718ffdc92d7f84dec37d64eeff
Tx public key: e7c60be740b59efd7b8d867c174cd378c2117a20042334a10bf438b7e5bd6ac1
Timestamp: 1737077981 Timestamp [UCT]: 2025-01-17 01:39:41 Age [y:d:h:m:s]: 00:307:00:35:43
Block: 1198990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216947 RingCT/type: yes/0
Extra: 01e7c60be740b59efd7b8d867c174cd378c2117a20042334a10bf438b7e5bd6ac102110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4d9a37f2f7a00c13d30bdf89595f477b0dc8fe7b0b1baee47d5ab1c40b7cb0a 0.600000000000 1685617 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": 1199000, "vin": [ { "gen": { "height": 1198990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4d9a37f2f7a00c13d30bdf89595f477b0dc8fe7b0b1baee47d5ab1c40b7cb0a" } } ], "extra": [ 1, 231, 198, 11, 231, 64, 181, 158, 253, 123, 141, 134, 124, 23, 76, 211, 120, 194, 17, 122, 32, 4, 35, 52, 161, 11, 244, 56, 183, 229, 189, 106, 193, 2, 17, 0, 0, 0, 11, 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