Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9428096af75306b5c412b380379459d1bc8f3290e995dc299ca6d6a3e1540780

Tx prefix hash: 246ce1790e38f3bddb92268bd6af4c42e4eaf219ee27aa85895afb9b2fe00c2f
Tx public key: f579b4128d03810475be267385ef89f6a5c025d564939df3196f6b55a3dedecd
Timestamp: 1705404006 Timestamp [UCT]: 2024-01-16 11:20:06 Age [y:d:h:m:s]: 01:322:05:49:03
Block: 936532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489159 RingCT/type: yes/0
Extra: 01f579b4128d03810475be267385ef89f6a5c025d564939df3196f6b55a3dedecd02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ea847e2503a52ef85299b5c2e7344ecd9b779f15f8d30bc50b4068fd9b62cb 0.600000000000 1394560 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": 936542, "vin": [ { "gen": { "height": 936532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ea847e2503a52ef85299b5c2e7344ecd9b779f15f8d30bc50b4068fd9b62cb" } } ], "extra": [ 1, 245, 121, 180, 18, 141, 3, 129, 4, 117, 190, 38, 115, 133, 239, 137, 246, 165, 192, 37, 213, 100, 147, 157, 243, 25, 111, 107, 85, 163, 222, 222, 205, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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