Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ec11244357853d9e25d31c808c6c28857f196e15a434e449b678d88c7ceef9

Tx prefix hash: 503ca337e8d0545b1929f167b93da2901f17b724b021c81b2ea540def574766b
Tx public key: aee9c4d6942f8c0bf77f19ee73746940170527ead4ce28a4eac8aa04515a1506
Timestamp: 1711439492 Timestamp [UCT]: 2024-03-26 07:51:32 Age [y:d:h:m:s]: 01:219:01:06:15
Block: 986611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415215 RingCT/type: yes/0
Extra: 01aee9c4d6942f8c0bf77f19ee73746940170527ead4ce28a4eac8aa04515a150602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c0804805ae9f51d498d12dfe7772dce0a5eeb303f5e1482de70dc4c1cd44c0a 0.600000000000 1446842 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": 986621, "vin": [ { "gen": { "height": 986611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c0804805ae9f51d498d12dfe7772dce0a5eeb303f5e1482de70dc4c1cd44c0a" } } ], "extra": [ 1, 174, 233, 196, 214, 148, 47, 140, 11, 247, 127, 25, 238, 115, 116, 105, 64, 23, 5, 39, 234, 212, 206, 40, 164, 234, 200, 170, 4, 81, 90, 21, 6, 2, 17, 0, 0, 0, 8, 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