Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f28f175ef93f1f39a5bd97ba3ee4bcf1d2b0c8ccf5f91986bfe408cf7ebbb94

Tx prefix hash: 0815de1faedacb457e2c8937b3c7526b164fff9602131ca4618fe2a5776f4a6a
Tx public key: 42b8b43affb1b1e751a374e21031de4bfd5019cbfb982f2c55101d4d61551cb0
Timestamp: 1746551368 Timestamp [UCT]: 2025-05-06 17:09:28 Age [y:d:h:m:s]: 00:205:05:28:16
Block: 1277159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144406 RingCT/type: yes/0
Extra: 0142b8b43affb1b1e751a374e21031de4bfd5019cbfb982f2c55101d4d61551cb0021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6df8abca38f6ee306b706c3406ac7fdb2256149c1fa1a370570d817b19381279 0.600000000000 1764510 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": 1277169, "vin": [ { "gen": { "height": 1277159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6df8abca38f6ee306b706c3406ac7fdb2256149c1fa1a370570d817b19381279" } } ], "extra": [ 1, 66, 184, 180, 58, 255, 177, 177, 231, 81, 163, 116, 226, 16, 49, 222, 75, 253, 80, 25, 203, 251, 152, 47, 44, 85, 16, 29, 77, 97, 85, 28, 176, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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