Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd224b2e47b5ffea2e1cb8003d8883a8f125e6f3f21e2204358493fe218690d8

Tx prefix hash: 0bb8e6649bdebd3d7d87bfced678d672f5c1168269a0d2d55bef5fcad28a5a9b
Tx public key: fa5ab8cf6b6c394095d834796c243ed58f8b590d8dd63f787005d7c45a466feb
Timestamp: 1725229596 Timestamp [UCT]: 2024-09-01 22:26:36 Age [y:d:h:m:s]: 00:087:16:31:11
Block: 1100910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62724 RingCT/type: yes/0
Extra: 01fa5ab8cf6b6c394095d834796c243ed58f8b590d8dd63f787005d7c45a466feb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa4bf79e10c7c6a3d0fa8403634659f6f19359ff0b09337af383c63e82534831 0.600000000000 1576891 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": 1100920, "vin": [ { "gen": { "height": 1100910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa4bf79e10c7c6a3d0fa8403634659f6f19359ff0b09337af383c63e82534831" } } ], "extra": [ 1, 250, 90, 184, 207, 107, 108, 57, 64, 149, 216, 52, 121, 108, 36, 62, 213, 143, 139, 89, 13, 141, 214, 63, 120, 112, 5, 215, 196, 90, 70, 111, 235, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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