Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94f1f44c24da313ab69095861fea7ed3398de70f72f22f4412414e746d0a977

Tx prefix hash: 332b27c53d1b153bec015aeb96b02e9a5d04d65b44de3c6c0ca24169055523fe
Tx public key: b280f96076214059ebb212f8ca42cdf068dd3c512c91ab25fb106555b161611c
Timestamp: 1633172210 Timestamp [UCT]: 2021-10-02 10:56:50 Age [y:d:h:m:s]: 03:089:06:07:31
Block: 345124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 840738 RingCT/type: yes/0
Extra: 01b280f96076214059ebb212f8ca42cdf068dd3c512c91ab25fb106555b161611c02110000000106faf294000000000000000000

1 output(s) for total of 44.103850995000 dcy

stealth address amount amount idx
00: 3ed8def4d06ea582b1d32d0bbf2d067d6b5448f29f076d3d16a2c6e13a39fe48 44.103850995000 707986 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": 345134, "vin": [ { "gen": { "height": 345124 } } ], "vout": [ { "amount": 44103850995, "target": { "key": "3ed8def4d06ea582b1d32d0bbf2d067d6b5448f29f076d3d16a2c6e13a39fe48" } } ], "extra": [ 1, 178, 128, 249, 96, 118, 33, 64, 89, 235, 178, 18, 248, 202, 66, 205, 240, 104, 221, 60, 81, 44, 145, 171, 37, 251, 16, 101, 85, 177, 97, 97, 28, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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