Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa131e94a0b6a67a5af4c09096b85213f922339b94f83c2159323259e8c73d54

Tx prefix hash: 24654522c700629e1a7142ef2501712742f264756e5f5c13c3d977e3f175efa0
Tx public key: 0dbfe50e866713c5eaf40d034734d365011a6820f66a47c3c34e53f7a8ef62fa
Timestamp: 1578452661 Timestamp [UCT]: 2020-01-08 03:04:21 Age [y:d:h:m:s]: 04:358:16:51:51
Block: 40938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145720 RingCT/type: yes/0
Extra: 010dbfe50e866713c5eaf40d034734d365011a6820f66a47c3c34e53f7a8ef62fa0211000000034ac5aa02000000000000000000

1 output(s) for total of 449.113653336000 dcy

stealth address amount amount idx
00: 8c0d3234dc21e544c3519fd69c4e949459ceab5c0ec0967bcacc99a57ebedae9 449.113653336000 72423 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": 40948, "vin": [ { "gen": { "height": 40938 } } ], "vout": [ { "amount": 449113653336, "target": { "key": "8c0d3234dc21e544c3519fd69c4e949459ceab5c0ec0967bcacc99a57ebedae9" } } ], "extra": [ 1, 13, 191, 229, 14, 134, 103, 19, 197, 234, 244, 13, 3, 71, 52, 211, 101, 1, 26, 104, 32, 246, 106, 71, 195, 195, 78, 83, 247, 168, 239, 98, 250, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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