Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4261ab724ea8687cc3709935f25694dc4c924418f128dcd39b52bb59945bd16

Tx prefix hash: 2a766811a61ebf9d7f61477326a41d5f98550e01b5d16cd1741f80e0b4274cd6
Tx public key: 7d4d6a40eb65220acf33996c0813cbceae722e1d96fdb96a019af09c4e1612f2
Timestamp: 1700874485 Timestamp [UCT]: 2023-11-25 01:08:05 Age [y:d:h:m:s]: 01:145:17:55:33
Block: 898997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365343 RingCT/type: yes/0
Extra: 017d4d6a40eb65220acf33996c0813cbceae722e1d96fdb96a019af09c4e1612f2021100000002faf35c9c000000000000000000

1 output(s) for total of 0.644539789000 dcy

stealth address amount amount idx
00: 4e1a3896fa42e3b8c410ae1a211f83a398c78521dd552bc88790ba06e6f5275e 0.644539789000 1355434 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": 899007, "vin": [ { "gen": { "height": 898997 } } ], "vout": [ { "amount": 644539789, "target": { "key": "4e1a3896fa42e3b8c410ae1a211f83a398c78521dd552bc88790ba06e6f5275e" } } ], "extra": [ 1, 125, 77, 106, 64, 235, 101, 34, 10, 207, 51, 153, 108, 8, 19, 203, 206, 174, 114, 46, 29, 150, 253, 185, 106, 1, 154, 240, 156, 78, 22, 18, 242, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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