Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 463a2f642e10f866d84a2b518ac375d4e30dfa7ddd28286c9cc4055f511aa747

Tx prefix hash: 88bac5c7c7369664e90bbe84bc97a4769fbdb46ab3ca909f5abbcbc368e6a563
Tx public key: ff25c6c5a0f4d37d1f0d29a67546be8589ea328523c2ec727b4788c484316995
Timestamp: 1730508420 Timestamp [UCT]: 2024-11-02 00:47:00 Age [y:d:h:m:s]: 00:143:22:48:30
Block: 1144585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102703 RingCT/type: yes/0
Extra: 01ff25c6c5a0f4d37d1f0d29a67546be8589ea328523c2ec727b4788c484316995021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b3d91b90c5de7b66865e577bd705d71b87150285a3c4ac167e5f8332032afb7 0.600000000000 1628844 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": 1144595, "vin": [ { "gen": { "height": 1144585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b3d91b90c5de7b66865e577bd705d71b87150285a3c4ac167e5f8332032afb7" } } ], "extra": [ 1, 255, 37, 198, 197, 160, 244, 211, 125, 31, 13, 41, 166, 117, 70, 190, 133, 137, 234, 50, 133, 35, 194, 236, 114, 123, 71, 136, 196, 132, 49, 105, 149, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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