Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970f287f26b367812be806a2bc3715d752234a20f397018d8826414f4651ae1b

Tx prefix hash: 7ce792bb716ecf4724d943b93d85c357d2c829f43ae95900d1a5b6d489a6a1be
Tx public key: 30cfe4a752697041d63a486b5320fbc208ef2b70e23bbf2df3998332cc3d7bd1
Timestamp: 1670307266 Timestamp [UCT]: 2022-12-06 06:14:26 Age [y:d:h:m:s]: 02:041:18:34:39
Block: 646471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551771 RingCT/type: yes/0
Extra: 0130cfe4a752697041d63a486b5320fbc208ef2b70e23bbf2df3998332cc3d7bd102110000000183600029000000000000000000

1 output(s) for total of 4.425610673000 dcy

stealth address amount amount idx
00: 19e924cfe53f19bee4b407e6684a4dd718d2ca05aea3e88ac17069aa3f7d06e2 4.425610673000 1086692 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": 646481, "vin": [ { "gen": { "height": 646471 } } ], "vout": [ { "amount": 4425610673, "target": { "key": "19e924cfe53f19bee4b407e6684a4dd718d2ca05aea3e88ac17069aa3f7d06e2" } } ], "extra": [ 1, 48, 207, 228, 167, 82, 105, 112, 65, 214, 58, 72, 107, 83, 32, 251, 194, 8, 239, 43, 112, 226, 59, 191, 45, 243, 153, 131, 50, 204, 61, 123, 209, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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