Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 519451f6668265a4ea4c4955bdb8488ecdaceee9c50de49776b52124a70d1414

Tx prefix hash: c7414f444872a10eb330e1b1645cd2e2927a2af76570ce8fa895e3f1881e4e4b
Tx public key: 35897dab42f5ec5b7d16f171a69b2c71e4d52e23ac4761651211fba67b5b04bf
Timestamp: 1720078788 Timestamp [UCT]: 2024-07-04 07:39:48 Age [y:d:h:m:s]: 00:150:02:51:40
Block: 1058203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107447 RingCT/type: yes/0
Extra: 0135897dab42f5ec5b7d16f171a69b2c71e4d52e23ac4761651211fba67b5b04bf0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9579d87f934bbb56e757c4dfe02f8c8b6738f5a19f93c18255e4f4c3b5d6ac4b 0.600000000000 1528652 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": 1058213, "vin": [ { "gen": { "height": 1058203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9579d87f934bbb56e757c4dfe02f8c8b6738f5a19f93c18255e4f4c3b5d6ac4b" } } ], "extra": [ 1, 53, 137, 125, 171, 66, 245, 236, 91, 125, 22, 241, 113, 166, 155, 44, 113, 228, 213, 46, 35, 172, 71, 97, 101, 18, 17, 251, 166, 123, 91, 4, 191, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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