Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 274937b7a0d01f1dea0cedfd6d4e2fa3eabc43eb62d4019a4cb1ef5827fe2f45

Tx prefix hash: f223a972b7cf1c247e5c525e84fbf90686723497f6f81f30fd69e948ab75164b
Tx public key: d41dc0899a66ec3ff091816b5bc0af90374288f736af9cb0ff4ca5faa4b95287
Timestamp: 1722124833 Timestamp [UCT]: 2024-07-28 00:00:33 Age [y:d:h:m:s]: 01:072:18:45:00
Block: 1075169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310463 RingCT/type: yes/0
Extra: 01d41dc0899a66ec3ff091816b5bc0af90374288f736af9cb0ff4ca5faa4b95287021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b412c9f23d06fff75697430570fb8297d29faca08f20cdc1b94d713f21c6cf5 0.600000000000 1547692 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": 1075179, "vin": [ { "gen": { "height": 1075169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b412c9f23d06fff75697430570fb8297d29faca08f20cdc1b94d713f21c6cf5" } } ], "extra": [ 1, 212, 29, 192, 137, 154, 102, 236, 63, 240, 145, 129, 107, 91, 192, 175, 144, 55, 66, 136, 247, 54, 175, 156, 176, 255, 76, 165, 250, 164, 185, 82, 135, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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