Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49931e5add83586fcc9d96a40c50681e171568d7a0a51cc7cd24566cd15252e5

Tx prefix hash: fc0f8c56b1f86eae1f346b8059cde503ada2953aee750c904649b3171eb25115
Tx public key: 7b46e48eac1c0127d5e535d1eb6f12319013ac743892e945a8515540f2a71654
Timestamp: 1727584769 Timestamp [UCT]: 2024-09-29 04:39:29 Age [y:d:h:m:s]: 01:039:01:42:44
Block: 1120438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286307 RingCT/type: yes/0
Extra: 017b46e48eac1c0127d5e535d1eb6f12319013ac743892e945a8515540f2a71654021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 827f0a870f00ab5bde518b1f1657d4dd63239b0ad5b6c15fa60d51374a26f288 0.600000000000 1602353 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": 1120448, "vin": [ { "gen": { "height": 1120438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "827f0a870f00ab5bde518b1f1657d4dd63239b0ad5b6c15fa60d51374a26f288" } } ], "extra": [ 1, 123, 70, 228, 142, 172, 28, 1, 39, 213, 229, 53, 209, 235, 111, 18, 49, 144, 19, 172, 116, 56, 146, 233, 69, 168, 81, 85, 64, 242, 167, 22, 84, 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