Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 773591b80f2df7e5b18655f5f879acbbbde54a1608090998a87019cddfd88e9d

Tx prefix hash: 27acdc3422e43d2341d0563676bf5f50d254f99d9bf1ec86a8eef1bdbd5e8ab4
Tx public key: e2ed6c39b6360413819667ea47088b86c2e5cc408218c0cbdf0f2ddc97f21c90
Timestamp: 1724640187 Timestamp [UCT]: 2024-08-26 02:43:07 Age [y:d:h:m:s]: 00:295:22:34:03
Block: 1096019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211300 RingCT/type: yes/0
Extra: 01e2ed6c39b6360413819667ea47088b86c2e5cc408218c0cbdf0f2ddc97f21c9002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2491950346b3ed572fcbaf1e8cf11f415565f02b4a4e77a75edfc263d45cf4f9 0.600000000000 1571206 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": 1096029, "vin": [ { "gen": { "height": 1096019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2491950346b3ed572fcbaf1e8cf11f415565f02b4a4e77a75edfc263d45cf4f9" } } ], "extra": [ 1, 226, 237, 108, 57, 182, 54, 4, 19, 129, 150, 103, 234, 71, 8, 139, 134, 194, 229, 204, 64, 130, 24, 192, 203, 223, 15, 45, 220, 151, 242, 28, 144, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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