Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e1d5cee5010b69bec8dc2ca02b28c6109d71e9dcac3110ce93ac5c9a4678da8

Tx prefix hash: 6bb148454ad69cc9db85d40fe188d857234fcdc02c9ae4bec92a4cced3b56bee
Tx public key: 8595e615b2efec72a72c41984e132fde52cf2a3a41b50673ca2554fbdcdba1d2
Timestamp: 1576424405 Timestamp [UCT]: 2019-12-15 15:40:05 Age [y:d:h:m:s]: 04:326:22:20:05
Block: 27350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119781 RingCT/type: yes/0
Extra: 018595e615b2efec72a72c41984e132fde52cf2a3a41b50673ca2554fbdcdba1d20211000000024943cd9f000000000000000000

1 output(s) for total of 498.171596788000 dcy

stealth address amount amount idx
00: a50b0a5899fc4019d60ba7145d2ae5b944681b1974dc4d7d0c6158ff247068db 498.171596788000 45346 of 0

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": 27360, "vin": [ { "gen": { "height": 27350 } } ], "vout": [ { "amount": 498171596788, "target": { "key": "a50b0a5899fc4019d60ba7145d2ae5b944681b1974dc4d7d0c6158ff247068db" } } ], "extra": [ 1, 133, 149, 230, 21, 178, 239, 236, 114, 167, 44, 65, 152, 78, 19, 47, 222, 82, 207, 42, 58, 65, 181, 6, 115, 202, 37, 84, 251, 220, 219, 161, 210, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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