Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c1708056465c7d604cb189032fb2c4cbe6059e46cb47d8d78a371fef3db71a5

Tx prefix hash: 45516e42842c33f658bb194862b17611c955c46ac70e085a3a3a6fa7edca5c38
Tx public key: 69d50631b3b0759c82f2512cb15e65a9f253875b8cc60d385cc4c46553c924be
Timestamp: 1705927911 Timestamp [UCT]: 2024-01-22 12:51:51 Age [y:d:h:m:s]: 01:288:23:53:44
Block: 940859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465347 RingCT/type: yes/0
Extra: 0169d50631b3b0759c82f2512cb15e65a9f253875b8cc60d385cc4c46553c924be02110000000358e72c11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68cc2da281d0c5af0c07c99ab80fae1ab07ec06011c8ce3b9c6a1342ae825ba8 0.600000000000 1398999 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": 940869, "vin": [ { "gen": { "height": 940859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68cc2da281d0c5af0c07c99ab80fae1ab07ec06011c8ce3b9c6a1342ae825ba8" } } ], "extra": [ 1, 105, 213, 6, 49, 179, 176, 117, 156, 130, 242, 81, 44, 177, 94, 101, 169, 242, 83, 135, 91, 140, 198, 13, 56, 92, 196, 196, 101, 83, 201, 36, 190, 2, 17, 0, 0, 0, 3, 88, 231, 44, 17, 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