Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1dcb7f070ba519431c82a1941d86c2f404a8c26121ac99c1a784924d3ca105

Tx prefix hash: 56024012c2d86a6ddde2b4626f34482d8e5d90234c022717385e86abd0f063ae
Tx public key: 44fc70dd6e30f1e73cd0fe531d7ad4c706a155a9a8d208766730c7083c766e19
Timestamp: 1681923877 Timestamp [UCT]: 2023-04-19 17:04:37 Age [y:d:h:m:s]: 02:025:19:17:23
Block: 742127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540616 RingCT/type: yes/0
Extra: 0144fc70dd6e30f1e73cd0fe531d7ad4c706a155a9a8d208766730c7083c766e190211000000085029cbac000000000000000000

1 output(s) for total of 2.133169631000 dcy

stealth address amount amount idx
00: 1feba835c266d33b2f6d55b4ad474d0addcc3817c06e789374ea9afab3b121b1 2.133169631000 1189084 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": 742137, "vin": [ { "gen": { "height": 742127 } } ], "vout": [ { "amount": 2133169631, "target": { "key": "1feba835c266d33b2f6d55b4ad474d0addcc3817c06e789374ea9afab3b121b1" } } ], "extra": [ 1, 68, 252, 112, 221, 110, 48, 241, 231, 60, 208, 254, 83, 29, 122, 212, 199, 6, 161, 85, 169, 168, 210, 8, 118, 103, 48, 199, 8, 60, 118, 110, 25, 2, 17, 0, 0, 0, 8, 80, 41, 203, 172, 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