Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438d99d1e56c1c8449717b279e234e5618ba9819674a2c4e622daca64d23bc0b

Tx prefix hash: 4ff8448064c34f0593718a4204771cb8b3fecb70d37acb45647f4881f43539d0
Tx public key: b4eab3a8b6e3055d5ea6fa6af4cf958bc9a80b92f904c407dfce23ecafd52363
Timestamp: 1621652253 Timestamp [UCT]: 2021-05-22 02:57:33 Age [y:d:h:m:s]: 03:219:14:07:57
Block: 264838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 918872 RingCT/type: yes/0
Extra: 01b4eab3a8b6e3055d5ea6fa6af4cf958bc9a80b92f904c407dfce23ecafd5236302110000002c0bb79a4a000000000000000000

1 output(s) for total of 81.373371043000 dcy

stealth address amount amount idx
00: 6ef32aa6932c5d0e291f7bae7d29fb4c792908da70973f92fb767546d5753e1c 81.373371043000 556806 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": 264848, "vin": [ { "gen": { "height": 264838 } } ], "vout": [ { "amount": 81373371043, "target": { "key": "6ef32aa6932c5d0e291f7bae7d29fb4c792908da70973f92fb767546d5753e1c" } } ], "extra": [ 1, 180, 234, 179, 168, 182, 227, 5, 93, 94, 166, 250, 106, 244, 207, 149, 139, 201, 168, 11, 146, 249, 4, 196, 7, 223, 206, 35, 236, 175, 213, 35, 99, 2, 17, 0, 0, 0, 44, 11, 183, 154, 74, 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