Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341ba1c2373d623f285f3ad62b312b0ab7327cce65ef99d1b6fb3ec9255e4a7b

Tx prefix hash: b268a033ec4b10b76880e2f02f37f277930dee3a68bee282f48ef5da22ff50ff
Tx public key: 7472ebe924a64b332b17e84231189db6353dc3ebf95a9d205f4194da271cc1cf
Timestamp: 1672049760 Timestamp [UCT]: 2022-12-26 10:16:00 Age [y:d:h:m:s]: 01:330:03:56:20
Block: 660906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496966 RingCT/type: yes/0
Extra: 017472ebe924a64b332b17e84231189db6353dc3ebf95a9d205f4194da271cc1cf02110000000afaf35c9c000000000000000000

1 output(s) for total of 3.964094850000 dcy

stealth address amount amount idx
00: 4cf35c4df5dc769ba50ce46da9593d5e91e4d3bc26cfadc7020c3134f3a3627e 3.964094850000 1101649 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": 660916, "vin": [ { "gen": { "height": 660906 } } ], "vout": [ { "amount": 3964094850, "target": { "key": "4cf35c4df5dc769ba50ce46da9593d5e91e4d3bc26cfadc7020c3134f3a3627e" } } ], "extra": [ 1, 116, 114, 235, 233, 36, 166, 75, 51, 43, 23, 232, 66, 49, 24, 157, 182, 53, 61, 195, 235, 249, 90, 157, 32, 95, 65, 148, 218, 39, 28, 193, 207, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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