Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd04a49a7f8184fdc37d1d91ab7ebed8af5e994ee313822a0078c618c189055

Tx prefix hash: 1e9a5678cd87757ea0b0176eca3c10902fa292fe1b5bd61602970ba3014be679
Tx public key: 2f7689e508d124886bec11a4a0cd42fd935c8e70a8798430c60126d9ddc6f65d
Timestamp: 1725051112 Timestamp [UCT]: 2024-08-30 20:51:52 Age [y:d:h:m:s]: 00:240:23:12:28
Block: 1099425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172104 RingCT/type: yes/0
Extra: 012f7689e508d124886bec11a4a0cd42fd935c8e70a8798430c60126d9ddc6f65d02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ed7b1d5fbd6400bd5b27a67a74218b1bcb1bab0394a0d1c4d6400e46650c7aa 0.600000000000 1575386 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": 1099435, "vin": [ { "gen": { "height": 1099425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ed7b1d5fbd6400bd5b27a67a74218b1bcb1bab0394a0d1c4d6400e46650c7aa" } } ], "extra": [ 1, 47, 118, 137, 229, 8, 209, 36, 136, 107, 236, 17, 164, 160, 205, 66, 253, 147, 92, 142, 112, 168, 121, 132, 48, 198, 1, 38, 217, 221, 198, 246, 93, 2, 17, 0, 0, 0, 12, 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