Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6279266cbee77958e9f7a88b41c2e0e8681b31e3ae7253950b961066a479d71e

Tx prefix hash: ab3e8d4a76cd59a99ecadfd21219d4359753686b7c873509c58a071729906c8d
Tx public key: 4fe91cf5095ca77467a1b3a023ab98cfdf4ba0754d7e445e73fd575f8ac68c19
Timestamp: 1725168911 Timestamp [UCT]: 2024-09-01 05:35:11 Age [y:d:h:m:s]: 00:219:00:54:40
Block: 1100405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156389 RingCT/type: yes/0
Extra: 014fe91cf5095ca77467a1b3a023ab98cfdf4ba0754d7e445e73fd575f8ac68c1902110000000523a894fd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48ab4705448612a7b84d7b436fb1a67e8ffe71dd9798011a04223bf9673688ec 0.600000000000 1576384 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": 1100415, "vin": [ { "gen": { "height": 1100405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48ab4705448612a7b84d7b436fb1a67e8ffe71dd9798011a04223bf9673688ec" } } ], "extra": [ 1, 79, 233, 28, 245, 9, 92, 167, 116, 103, 161, 179, 160, 35, 171, 152, 207, 223, 75, 160, 117, 77, 126, 68, 94, 115, 253, 87, 95, 138, 198, 140, 25, 2, 17, 0, 0, 0, 5, 35, 168, 148, 253, 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