Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0053a88ed92e1fad3301fbf4de3fae235770e6432fc71111b94619ea1d44c55a

Tx prefix hash: fccfab07679bbf90a818b442b78bf8f88fac0204746e4c075c8a94f1bac56b4e
Tx public key: b27b88e514a5883c19d73eda52d11a945c826c2f129e4bf6e70402ee8f09e494
Timestamp: 1730002963 Timestamp [UCT]: 2024-10-27 04:22:43 Age [y:d:h:m:s]: 00:159:11:46:53
Block: 1140446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113790 RingCT/type: yes/0
Extra: 01b27b88e514a5883c19d73eda52d11a945c826c2f129e4bf6e70402ee8f09e494021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fed56a77f8614b1b4bd83a3b420cf2f367a915a8d660db662c961f88c2ca7416 0.600000000000 1624245 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": 1140456, "vin": [ { "gen": { "height": 1140446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fed56a77f8614b1b4bd83a3b420cf2f367a915a8d660db662c961f88c2ca7416" } } ], "extra": [ 1, 178, 123, 136, 229, 20, 165, 136, 60, 25, 215, 62, 218, 82, 209, 26, 148, 92, 130, 108, 47, 18, 158, 75, 246, 231, 4, 2, 238, 143, 9, 228, 148, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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